IDOC --- XI. queue Id PACKAGE, Job ID EVENT_DRIVEN_XI , waiting long

Hi forum
I have a IDOC--->XI scenario,
when the IDOC comes, i can see in the MONI ... there is a QueueID PACKAGE,
and JobID as EVENT_DRIVEN_XI .
and the processing waits for a long time,
wahts the problem,
pls help

your message might be stuck in the queue,
you can use the following transactions for monitoring the queues
· SMQ1 qRFC Monitor for the outbound queue You can use this to monitor the status of the LUWs in the outbound queue.
· SMQ2 qRFC Monitor for the inbound queue. You can use this to monitor the status of the LUWs in the inbound queue.
· SMQS You can use the Outbound Queue Scheduler to register, deregister, and exclude destinations.
· SMQR You can use the Inbound Queue Scheduler to register and deregister queues

Similar Messages

What is the difference in the System Event triggers: Any queue limit set to zero and System queue reached its job limit

My co-worker and I are not sure what the difference between Any queue limit set to zero and System queue reached its job limit are in the System Events.

Hi jlayton,
System queue limit is the sum of all queue limits you have defined. For example, if you have a system queue limit of, say, 100 -- queue A has 50 jobs active, and queue B also has 50 jobs active, then you will receive an alert System queue reached its job limit since it is set to 100.
Any queue limit set to zero. Note, this may also include the System queue. For example, if you want to gracefully stop Tidal, you may want to set system queue = 0 so that there are no active jobs. When you do this, you will receive an alert queue limit set to zero.
BR,
Derrick Au

Background job is running for long tome in source system (ECC)

Hi All,
Background job is running for long tome in source system (ECC) while extracting data to PSA.
I checked in ECC system SM66,SM50 the job is still running
in SM37 the job is Active
There are only maximum 7000 records the extractor is 2LIS_02_ITM but it is taking 11 to 13 hours to load to PSA daily
I had checked enhancements every thing is correct.
Please help me on this how can I solve this issue.
Regards
Supraja K

Hi sudhi,
The difference between Call customer enhancement... and Result of customer enhancement:... is very less we can say this as a second.
The difference is between LUWs confirmed and 1 LUWs -
   and Call customer enhancement -
Please find the job log details below, and give me the solution to ressolve this
01:06:43 ***01:06:43 * ztta/roll_extension........... 2000000000                              *                 R8           050
                 R8           048
01:06:43 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA     RSQU          036
06:56:31 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 5.208 records                  R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5.208 records                      R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 PSA=1 USING SMQS SCHEDULER / IF [tRFC=ON] STARTING qRFC ELSE STARTING SAPI                 R3           299
06:56:31 Synchronous send of data package 1 (0 parallel tasks)                                      R3           410
06:56:32 tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =                           R3           038
06:56:32 tRFC: Start = 00.00.0000 00:00:00, End = 00.00.0000 00:00:00                               R3           039
06:56:32 Synchronized transmission of info IDoc 3 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 3, IDoc No. 1549822, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Altogether, 0 records were filtered out through selection conditions                      RSQU          037
06:56:32 Synchronized transmission of info IDoc 4 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 4, IDoc No. 1549823, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Job finished                                                                               00           517
Regards
Supraja

ERRORImport Monitor jobs: running 0, waiting 1, completed 17, failed 1,

Hello,
I am installing ECC 6.0 on database Maxdb7.6. window 2003 service pack 2 processor AMD 3400 RAM 2 GB,
I am getting the following error at the ERRORImport Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
WARNING 2010-10-29 22:40:15
Execution of the command "C:\j2sdk1.4.2_09\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ADA -importDirs D:\Ides\exportdb\db1\EXP1;D:\Ides\exportdb\db2\EXP2;D:\Ides\exportdb\db3\EXP3;D:\Ides\exportdb\db4\EXP4;D:\Ides\exportdb\db5\EXP5;D:\Ides\exportdb\db6\EXP6;D:\Ides\exportdb\db6\EXP7;D:\Ides\exportdb\db6\EXP8;D:\Ides\exportdb\db6\EXP9;D:\Ides\exportdb\db6\EXP10;D:\Ides\exportdb\db6\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS" -orderBy "" -r3loadExe E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -nolog -c 0" -trace all -sapinst" finished with return code 103. Output: java version "1.4.2_09"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)Import Monitor jobs: running 1, waiting 1, completed 17, failed 0, total 19.Loading of 'SAPSSEXC' import package: ERRORImport Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
ERROR 2010-10-29 22:40:15
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2010-10-29 22:40:15
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
import_monitor.java.log
java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 17, failed 0, total 19.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
PLZ help me
Thanks&regards
Vijay kumar
Moved from ABAP, General
Edited by: kishan P on Nov 2, 2010 10:17 AM

ERROR: 2010-10-29 22:07:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2010-10-29 22:07:56
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2010-10-29 22:07:56
1 error(s) during processing of packages.
INFO: 2010-10-29 22:07:56
Import Monitor is stopped.
INFO: 2010-10-29 22:39:45
Import Monitor is started.
CONFIG: 2010-10-29 22:39:45
Application options:
dbCodepage=4103
dbType=ADA
extFiles=no
importDirs=D:\Ides\exportdb\db1\EXP1;D:\Ides\exportdb\db2\EXP2;D:\Ides\exportdb\db3\EXP3;D:\Ides\exportdb\db4\EXP4;D:\Ides\exportdb\db5\EXP5;D:\Ides\exportdb\db6\EXP6;D:\Ides\exportdb\db6\EXP7;D:\Ides\exportdb\db6\EXP8;D:\Ides\exportdb\db6\EXP9;D:\Ides\exportdb\db6\EXP10;D:\Ides\exportdb\db6\EXP11
installDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS
jobNum=3
loadArgs= -nolog -c 0
monitorTimeout=30
orderBy=
r3loadExe=E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2010-10-29 22:39:45
List of packages with table structure: 'SAP0000'.
CONFIG: 2010-10-29 22:39:45
List of packages with views: 'SAPVIEW'.
TRACE: 2010-10-29 22:39:45 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS\DDLADA.TPL' template file is started.
INFO: 2010-10-29 22:39:45 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS\DDLADA.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2010-10-29 22:39:45
Data codepage 4103 is determined using TOC file 'D:\Ides\exportdb\db1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
TRACE: 2010-10-29 22:39:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2010-10-29 22:39:45 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -nolog -c 0
ERROR: 2010-10-29 22:39:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2010-10-29 22:40:15
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2010-10-29 22:40:15
1 error(s) during processing of packages.
INFO: 2010-10-29 22:40:15
Import Monitor is stopped.

Extraction jobs waits long time

Hi,
I tried to extract 0ORGUNIT information from one of our test systems.
As can be read from the job log at the end, the jobs sits and waits for about 14 hours before actually starting data extraction. We're talking a mere 46.000 entries here. I'm trying to understand why the jobs waits soo long.
Any idea is welcome?
16:17:18 Job started
16:17:18 Step 001 started (program SBIE0001, variant &0000000100868, user name 972044)
16:17:19 DATASOURCE = 0ORGUNIT_ATTR
16:17:19 *************************************************************************
16:17:19 *           Current values of selected profile parameter                *
16:17:19 *************************************************************************
16:17:19 * abap/heap_area_nondia......... 2000683008                              *
16:17:19 * abap/heap_area_total.......... 2000683008                              *
16:17:19 * abap/heaplimit................ 40894464                                *
16:17:19 * zcsa/installed_languages...... NEFD                                    *
16:17:19 * zcsa/system_language.......... E                                       *
16:17:19 * ztta/max_memreq_MB............ 64                                      *
16:17:19 * ztta/roll_area................ 10485760                                *
16:17:19 * ztta/roll_extension........... 2000683008                              *
16:17:19 *************************************************************************
05:54:05 BEGIN BW_BTE_CALL_BW204020_E 46.091
05:54:05 END BW_BTE_CALL_BW204020_E 46.091
05:54:05 BEGIN EXIT_SAPLRSAP_002 46.091
06:29:42 END EXIT_SAPLRSAP_002 46.091
06:29:42 Asynchronous sending of data package 000001 in task 0002 (1 parallel tasks)
06:30:33 tRFC: Data package = 000001, TID = 2DDE00246B9444ED2B370016, duration = 00:00:46, ARFCSTATE =
06:30:33 tRFC: Begin = 24.08.2006 06:29:47, End = 24.08.2006 06:30:33
06:30:33 Job finished

Gimmo,
Apart from my interactive session and the batch job nothing happens on the system.
sm50 shows no activity other than mine.
Sufficient resources are available.
What I do see in sm12 (locks) is:
Cli User         Time       Mode   Table      Lock argument
040 972044       09:27:24   E      EDIDC      0400000000005084008
Selected lock entries:              1
I suspect somethings not right in the ALE arena?
Regards,
Eric

Job output is no longer available in the database control file

Im running my rman backup with Oracle Enterprise manager grid control 10.2.0.1.
In nocatalog mode.
When I look for the job output in the "View Backup Report" section, it says
Job output is no longer available in the database control file.
Here is my rman setup:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 7;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 5 G;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/app/oracle/product/10.2.0/db_1/dbs/snapcf_mus_prod.f'; # default
anyone knows why i cannot see my rman job output?

show parameter control_file_record_keep_time;
NAME TYPE VALUE
control_file_record_keep_time integer 7
The backup is usually the last one. And it's the day before.
If i go to the JOB tab in oem, then click on the job detail, i can see the detail of my rman backup. But i cannot see the backup detail in the View Backup Report section off the database. It says the error message : Job output is no longer available in the database control file

REP-56093: Cached output for job 1058 is no longer valid.

When i run report, this error message showed up.
REP-52251: The output of job ID 1058 requested on Wed May 18 11:18:54 KST 2011 cannot be retrieved.
REP-56093: Cached output for job 1058 is no longer valid.
I tested like below.
When add rownum < 100 condition, the reports run well.
When no rownum condition, the reports failed to run.
Are there anyone to tell me the key point to solve this problem ???
I use weblogic and fussion middleware.
Edited by: backsulee on 2011. 5. 17 오후 7:31

metalink note " REP-56093: Cached Output For Job <###> Is No Longer Valid Running Large Report [ID 305398.1]" maybe does give the answer for you

Jobs stays in waiting state but does not ever run in target system

This usually happens when there is a network problem or the target system is down for some reason. Is there a way to ignore the waiting status so that the next scheduled job runs would be affected? If not can CPS be configured to constantly request for the actual status of the job in the target system?

Hi,
Set the below parameter on the process server of the target system for which jobs stays in waiting state.
Parameter: SAP_MaxReconnectTime value: 60
Reason: Process servers tries to connect to Target system at the time when the network issue happens and due to that It does not connect to the target SAP system and all the jobs stays in waiting status.
When you set this parameter with the value (what ever you want in Minutes), it will automatically try to reconnect to the target SAP System at every 60 min (or the value provided) when ever it loses the connection with Target system and Jobs will start processing again.
Thanks and Regards,
Vipul Kaswala

Reports6i: Server job queue API package

Hi,
Has anyone tried editing the reports server job queue API (rw_server.clean_up_queue)? I don't want the queue table (RW_SERVER_QUEUE) to be truncated each time the server is shutdown and re-started.
(By the way, it's mentioned in the Publishing Reports manual that we can edit the API package to override the default behaviour)
I did the following:
1. I commented the truncation commands in the rw_server.clean_up_queue function
2. Stop and re-start the server.
3. The reports server inserts duplicate records for scheduled jobs.
Apparently, Oracle Reports server component stores job queue information somewhere on the hard disk(c:\orant\reports60\server) and re-inserts that info. to the database table on queue startup without checking for duplicate job_ids.
I would appreciate if someone could try this and confirm it. Is this a bug?
Thanks
Manish

You can trace the report on the reports server. This link talks about tracing from reports builder but also has links and examples of how to set up tracing on the reports server.

Receiving binary IDOC via Queue and convert it to XML-IDOC

Hello,
we are focusing the following scenario:
We receive an plain, binary IDOC in a MQSeries Queue. We want to pick it, transform it and place it into R/3 (of course using XI 3.0). Afterwards the other way around.
I know the Howto for the ABAP mapping from XML-Idoc to plain IDOC. This may also work for our scenario. Do you agree?
The other way around is more difficult. I assume that - since the IDOC adapter resides in the ABAP stack - we cannot re-use an existant adapter module in the JMS adapter. Right?
I heared about JCO capabilities of "xmlizing" Idocs - but did not find hints within the javadoc. Anyway, would this really be the preferred way - writing an user exit for the adapter using JCO - to handle this? There must be a way to do it better, must it not?
How did you guys face this problem - I think its a common one...
Any starting points for a discussion are appreciated....
Greets,
helge

Hi Helge,
For the conversion of the incoming flat message, one could imagine a similar ABAP mapping as the one described for the XML->flat message conversion. The function module IDX_IDOC_TO_XML could be a good starting point for your search.
To perform conversions in the Java stack (e.g. in an adapter module) might be a quite complex task since you first have to get the IDoc metadata. And there you cannot reuse existing function modules.
Best regards
Joachim

Queue / Support package issue

Hi everyone!
Can someone give me direction on resolving the following issue?
Ssytem: SAP ECC 6.0
I first updated the Kernel from level 58 to 83. eveything went fine from what I can see.
Then I have been importing a queue to implement some Support Packages. the import has now stopped with the following errors:
I am not too sure what it all means and where to go from there.
Thank you for any explanations or suggestions
Regards
Corinne
1 ETP199X######################################
1 ETP152 TESTIMPORT
1 ETP101 transport order     : "SAPK-60007INISOIL"
1 ETP102 system              : "QAS"
1 ETP108 tp path             : "tp"
1 ETP109 version and release : "370.00.09" "700"
2EETW165 Function "OIUREP_GET_RECENT_ROYHIST (OIUREP_ROY_HISTORY|05)" does not fit into the existing function group "(OIUREP_ROY_REPORTING|09)".
2 ETW167 Please transport the whole function group.
2EETW165 Function "OIUREP_GET_RECENT_VOLHIST (OIUREP_ROY_HISTORY|06)" does not fit into the existing function group "(OIUREP_ROY_REPORTING|10)".
2 ETW167 Please transport the whole function group.
1 ETP152 TESTIMPORT
1 ETP110 end date and time   : "20070213113558"
1 ETP111 exit code           : "8"
1 ETP199 ######################################

Hi Ammey and others ,
The queue import failed with the same error.
I have found in note 822379 that this message can actually be ignored.
SAPK-60006INISOIL - SAPK-60007INISOIL
           Symptom: If the Support Packages SAPK-60006INISOIL und SAPK-60007INISOIL are imported together in a queue, the TEST_IMPORT step returns an error for Support Package SAPK-60007INISOIL. The following error messages are displayed in the test import log:
Function OIUREP_GET_RECENT_ROYHIST (OIUREP_ROY_HISTORY 05)
   does not fit into the existing function group.
   (OIUREP_ROY_REPORTING 09)
Function OIUREP_GET_RECENT_VOLHIST (OIUREP_ROY_HISTORY 06)
   does not fit into the existing function group.
   (OIUREP_ROY_REPORTING 10)
           Solution: You can ignore this error by choosing 'Extras'-> 'Ignore test-import error'. The error will not occur during the later import.
based on your latest message (2.39 PM) suggesting to ignore "Warnings" I should be able to mark the queue now as "Ignore test-import errors" and bypass my original error. That was the only error of type 8 or above.
Thank you
Corinne

IDOCs are queued up In Integration Server

Folks ,
I am not able to process the iDOCS as they are choked up in Integration server with following trace , can anybody help me out
<i><b> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:TimeSent>2006-04-19T18:43:47Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>BS_STG_R3_902_NA</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BS_DEV_R3_950_CS</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>B4ydE1e/NPq9tEnsDcj7vA==</SAP:ObjectId>
<SAP:SWCV>U0Q4sKe1Edqe7daFZAcBUQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2006-04-19T18:43:47Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
<SAP:MessageId>44452091-7B42-40B7-E100-000064070151</SAP:MessageId>
<SAP:Info>FIDCC2.0000000018113400:20060419144347</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2006-04-19T18:43:47Z" wasRead="false">
<SAP:Engine type="IS">is.61.sun081</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
- <SAP:Branch>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:Service>BS_DEV_R3_950_CS</SAP:Service>
</SAP:Branch>
- <SAP:Branch>
<SAP:MessageId>4445B42B-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:Service>BS_DEV_R3_R1D_201_IE</SAP:Service>
</SAP:Branch>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>902</SAP:MANDT>
<SAP:DOCREL>31I</SAP:DOCREL>
<SAP:DOCNUM>0000000018113400</SAP:DOCNUM>
<SAP:DIRECT>1</SAP:DIRECT>
<SAP:IDOCTYP>FIDCCP01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>FIDCC2</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPST4</SAP:SNDPOR>
<SAP:SNDPRN>ST4-902</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>A000000015</SAP:RCVPOR>
<SAP:RCVPRN>R3DCLNT950</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL>20060419144347</SAP:SERIAL>
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>30</SAP:STATUS>
<SAP:OUTMOD>2</SAP:OUTMOD>
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2006-04-19</SAP:CREDAT>
<SAP:CRETIM>14:43:47</SAP:CRETIM>
<SAP:ARCKEY />
</SAP:IDocInbound>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20060419</SAP:Date>
<SAP:Time>144347</SAP:Time>
<SAP:Host>sun081</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>61</SAP:SystemNr>
<SAP:OS>SunOS</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>012</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>XIAPPL</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>5DC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:PipelineService>
<SAP:QIdInternal>XBTOD___0000</SAP:QIdInternal>
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:ParentId ChildNo="0" ChildTotal="0">444520917B4240B7E100000064070151</SAP:ParentId>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="401">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">6407015140B8444684E320CC</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID">6407015E1C50444684E39DF5</SAP:EOReferenceInbound>
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>18029</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>18029</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IDOC</SAP:AdapterInbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>24</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.424552</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.443929</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.443977</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.613713</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.616273</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.625803</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.626241</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.634135</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.634561</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.645671</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.645716</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPST4</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">ST4-902</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">A000000015</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">R3DCLNT950</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">FIDCC2</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">FIDCCP01</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP" />
</SAP:DynamicConfiguration>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: XIAPPL</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">Correct Version from 2 to 3: 3.X-Data to 4.x-Data</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPST4</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 401</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAPPL</Trace>
<Trace level="1" type="Timestamp">2006-04-19T18:43:47Z EST</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 444520917B4240B7E100000064070151</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 401</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAPPL</Trace>
<Trace level="1" type="Timestamp">2006-04-19T18:43:47Z EST</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 2</Trace>
<Trace level="1" type="T">Multi-receiver split case</Trace>
<Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
<Trace level="1" type="T">Persisting split messages (split kids)</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOD___0000</Trace>
<Trace level="1" type="T">Persisting split kid = 4445B42A672D40B8E100000064070151</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope></b></i>

Hi Manish,
but you have to register the queues
go to SXMB_ADM and register queues option
it's one of the installation/configuration steps
you have to do it for any kind of message message exchange (if the person who installed XI didn't do it)
register the queues and restart the messages
or F6 at the queue entry
Regards,
michal

Outbound Idocs in queue?

Hi
Quick question:
If an Idoc is sent from SAP to XI and XI system is down - is this Idoc always placed into an RFC queue or can it just be retained in SAP with yellow status until it can be processed again?
Thanks
regards Ole

Hi,
Please note the following points:
1) Every message has a default priority assigned to it
2) You can change the priority
3) If the message with lowest priority is stuck in the queue for a very long time then it might be archived or deleted...this task is performed by system Admin.
So your message must satisfy the priority norm to surrive for a long time in the queue.
Regards,
Abhishek.

Direct printing, disable queuing of print jobs

I have some label printers that are connected to touch screen macs that we use for checking people in, setup like a kiosk. I would like to have it print directly to the printer without them being queued up on the mac. When the labels run out or jam, dozens of jobs get stuck in the queue, and you can't tell it by looking at the computer (dock is hidden). My preference is that when that happens, the computer would instead of adding to the backed up queue, it would hang on the print job and would not allow any more activity on the computer until the printer was attended to. So what I am asking is: Is there a way like in the "old days" of mac, is to directly print to a printer without it going to the queue first?

Short answer - no.

Report Queue Manager - Scheduled Jobs

Question: How/where does the Queue Manager store info for scheduled jobs?

It is possible (IN 9iAS) to configure the Reports Server to store all requests in a database table. The Table(s) / View(s) are created by the script rw_server.sql located in $ORACLE_HOME/reports/admin/sql
To configure this options, create the table and view with the rw_server.sql script, then add these lines in the
<reports server name>.conf file <jobStatusRepository class="oracle.reports.server.JobRepositoryDB"> <property name="repositoryConn" value="user/password@tnsalias" confidential="yes" encrypted="no"/> </jobStatusRepository> The "value" attribute of the property "repositoryConn" should be a user/password@tnsalias that will be used to connect to the database. The account must have access to the tables created by the script rw_server.sql The combination confidential="yes" and encrypted="no" will provoke the encryption of the value attribute once the Report Server is re-started : After the Reports Server has started you will find: <jobStatusRepository class="oracle.reports.server.JobRepositoryDB"> <property name="repositoryConn" value="ihjFFBFD3jk5Xfrd5HeX5w3dE/E=" confidential="yes" encrypted="yes"/> </jobStatusRepository> Description of the rw_server_queue view columns can be found in the script rw_server.sql itself.
Thanks,

IDOC --- XI. queue Id PACKAGE, Job ID EVENT_DRIVEN_XI , waiting long

Similar Messages

Maybe you are looking for