Report ending in warning with status 127 error

Hi,
We ran a concurrent report with Print options set for a custom report.
The report is ending in warning with the below error:
------------- 1) PRINT   -------------
Printing output file.
Request ID : 356879180
Number of copies : 1
Printer : ABSC_5WCC_HP9
/bin/sh: jforasnd: not found.
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 127
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 127.
Action: Review your concurrent request log file for more detailed information.
Please suggest how to overcome this error.
Regards
Siva G

Please see your other thread -- Re: Concurrent report ending in warning with status 127 (post upgrade to R12.1.

Similar Messages

Concurrent report ending in warning with status 127 (post upgrade to R12.1.

Hi,
We ran a concurrent report with Print options set for a custom report.
The report is ending in warning with the below error:
------------- 1) PRINT   -------------
Printing output file.
Request ID : 356879180
Number of copies : 1
Printer : ABSC_5WCC_HP9
/bin/sh: jforasnd: not found.
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 127
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 127.
Action: Review your concurrent request log file for more detailed information.
Please suggest how to overcome this error.
Regards
Siva G

We ran a concurrent report with Print options set for a custom report.What is the type of this report?
The report is ending in warning with the below error:Can you find any details in the OPP/CM log files?
/bin/sh: jforasnd: not found.Is jforasnd used in your report? Were you able to compile the report from Reports Builder with no issues?
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 127
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 127.
Action: Review your concurrent request log file for more detailed information.This is a generic error, so if none of the above helps please enable trace/debug, submit the request again and post the contents of the log file here.
Thanks,
Hussein

XML Publisher report ends in Warning with java.lang.OutOfMemoryError

Hi,
We are modifying the standard report Account Analysis Report (in Subledger Accounting) to create a custom report.
When run wide open, it is ending in Warning with the error java.lang.OutOfMemoryError in OPP Log.
We are on EBS 12.1.3. DB 11.2.0.3 and XML Publisher 5.6.3
We have set the below parameters in the data definition:
Use XML Publishers XSLT processor: True
Enable Scalable feature of XSLT processor: True
Enable XSLT Runtime optimization: True
Also we have added these to the Data template:
<property name="db_fetch_size" value="20" />
<property name="scalable_mode" value="on" />
On the concurrent program, we have this option set:
-ms1024m -mx2048m
Still, the program is ending in Warning and not producing output. Any pointers here?
We can also see that the Temporary Directory is not able to be set on the data definition. Why is this?
After setting the Temporary Directory from Administration page, we were able to set the temporary directory for this data definition, but that did not solve the iseue.

Glad you have sorted this - note that the fnd_concurrent_requests table has the fields pp_Start_date and pp_end_date which will show how long post processing is taking.
Good to a good idea to monitor this in relation to the setting you have made in the profile option Concurrent:OPP Timeout profile option though 3 hours should cover most things!!!!

Adalnctl.sh: exiting with status 127

Hi all,
I just clonned 11i, but noticed that when I restart apps tier I am getting "exiting with status 1" message.
Looked at the log and found:
Setting service OracleTNSListener80APPS_SPIUAT_finappstest01kt to mode 2
Executing service control script:
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh start
Timeout specified in context file: 100 second(s)
script returned:
adalnctl.sh version
Checking for FNDFS executable.
Starting listener process APPS_SPIUAT.
adalnctl.sh: exiting with status 127
.end std out.
.end err out.
Where do I start?
Thanks,
Eugene

Here is what adalnctl.txt shows. Could you please tell me if patch that you mentioned references these errors?
cat adalnctl.txt
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 127: lsnrctl: command not found
Starting listener process APPS_SPIUAT.
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 138: lsnrctl: command not found
adalnctl.sh: exiting with status 127
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 156: lsnrctl: command not found
Listener APPS_SPIUAT has already been stopped.
adalnctl.sh: exiting with status 2
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 127: lsnrctl: command not found
Starting listener process APPS_SPIUAT.
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 138: lsnrctl: command not found
adalnctl.sh: exiting with status 127
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 156: lsnrctl: command not found
Listener APPS_SPIUAT has already been stopped.
adalnctl.sh: exiting with status 2
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 127: lsnrctl: command not found
Starting listener process APPS_SPIUAT.
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 138: lsnrctl: command not found
adalnctl.sh: exiting with status 127
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 156: lsnrctl: command not found
Listener APPS_SPIUAT has already been stopped.
adalnctl.sh: exiting with status 2
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 127: lsnrctl: command not found
Starting listener process APPS_SPIUAT.
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 138: lsnrctl: command not found
adalnctl.sh: exiting with status 127
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 156: lsnrctl: command not found
Listener APPS_SPIUAT has already been stopped.
adalnctl.sh: exiting with status 2
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 127: lsnrctl: command not found
Starting listener process APPS_SPIUAT.
/uat/appluat/comn/admin/scripts/SPIUAT_finappstest01kt/adalnctl.sh: line 138: lsnrctl: command not found
adalnctl.sh: exiting with status 127

The Lync Server Front-End service terminated with service-specific error %%-1008124893.

Hello, everyone
I've installed Lync Server 2010. There was no error during installation. But when i start Lync Server Front End Server, i'm getting following error:
The Lync Server Front-End service terminated with service-specific error %%-1008124893.
In event viewer:
The evaluation period for Microsoft Lync Server 2010 has expired. Please upgrade from the evaluation version to the fully licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
Cause: The evaluation period for Microsoft Lync Server 2010 has expired.
I've upgraded Lync Server according to http://technet.microsoft.com/en-us/library/gg521005.aspx?ppud=4
Also I've installed all Lync Server updates.
But I still could not start Lync Front End Sever. How can I solve this problem?
Thanks

Hi,
Can you try to run
start-cswindowsservice -report c:\report.html
and post the report so we can have more information about your problem ?
Regards,
Adrian TUPPER - ABC Systemes - http://thelyncexperience.blog.com/ If answer is helpful, please hit the green arrow on the left, or mark as answer Thank you

Adalnctl failed to start with status 127

OS:red hat as4
ebs: 11.5.9
now my system can be started,but the adalnctl failed to start with status 127.
the error message is about lsnrctl which saied that lsnrctl: command not found.
but when i start the lsnrctl with oracle owner,the lsnrctl was started immediately.
however,i found that,the lsnrctl was conected to the port 1521,the adalnctl to the port 1626.
please help me to see it!
the cdalnctl log was this:
LSNRCTL for Linux: Version 9.2.0.3.0 - Production on 20-MAY-2009 17:03:27
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=TCP)(Host=ebstest)(Port=1626))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux Error: 111: Connection refused
Starting listener process APPS_PROD.
LSNRCTL for Linux: Version 9.2.0.3.0 - Production on 20-MAY-2009 17:03:27
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Starting /u01/oradata/prodora/8.0.6/bin/tnslsnr: please wait...
TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
Linux Error: 2: No such file or directory
adalnctl.sh: exiting with status 1
Checking status for listener process APPS_PROD.
adalnctl.sh: exiting with status 1
./adalnctl.sh: line 126: lsnrctl: command not found
Starting listener process APPS_PROD.
./adalnctl.sh: line 137: lsnrctl: command not found
adalnctl.sh: exiting with status 127
Checking status for listener process APPS_PROD.
adalnctl.sh: exiting with status 1

oh maybe i found it
i have more than one listener.ora
[root@ebstest /]# find -name listener.ora
./u01/oradata/prodora/iAS/hs/admin/listener.ora
./u01/oradata/prodora/iAS/network/admin/samples/listener.ora
./u01/oradata/prodora/8.0.6/network/admin/samples/listener.ora
./u01/oradata/prodora/8.0.6/network/admin/PROD_ebstest/listener.ora
./u01/oradata/proddb/9.2.0/network/admin/samples/listener.ora
./u01/oradata/proddb/9.2.0/network/admin/PROD_ebstest/listener.ora
./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010106/listener.ora
./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010108/listener.ora
./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010121/listener.ora
and the other listener.ora was about port 1626
[root@ebstest /]# cat ./u01/oradata/prodora/8.0.6/network/admin/PROD_ebstest/listener.ora
# $Header: admk80ln_ux.sql 115.13 2003/04/03 08:05:06 skghosh noship $
# LISTENER.ORA For Oracle Applications
# This file is automatically generated
APPS_PROD =
(ADDRESS_LIST =
(ADDRESS= (PROTOCOL= TCP)(Host= ebstest)(Port= 1626))
SID_LIST_APPS_PROD =
(SID_LIST =
( SID_DESC = ( SID_NAME = FNDSM_PROD )
( ORACLE_HOME = /u01/oradata/prodora/8.0.6 )
( PROGRAM = /u01/oradata/prodappl/fnd/11.5.0/bin/FNDSM )
( envs='MYAPPSORA=/u01/oradata/prodappl/APPSPROD_ebstest.env,PATH=/usr/bin:/usr/ccs/bin:/bin,FNDSM_SCRIPT=/u01/oradata/prodcomn/admin/scripts/PROD_ebstest/gsmstart.sh' )
( SID_DESC = ( SID_NAME = FNDFS )
( ORACLE_HOME = /u01/oradata/prodora/8.0.6 )
( PROGRAM = /u01/oradata/prodappl/fnd/11.5.0/bin/FNDFS )
( envs='EPC_DISABLED=TRUE,NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1,LD_LIBRARY_PATH=/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,SHLIB_PATH=/usr/lib:/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,LIBPATH=/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,APPLFSTT=PROD,APPLFSWD=/u01/oradata/prodappl/admin' )
STARTUP_WAIT_TIME_APPS_PROD = 0
CONNECT_TIMEOUT_APPS_PROD = 10
TRACE_LEVEL_APPS_PROD = OFF
LOG_DIRECTORY_APPS_PROD = /u01/oradata/prodora/8.0.6/network/admin
LOG_FILE_APPS_PROD = APPS_PROD
TRACE_DIRECTORY_APPS_PROD = /u01/oradata/prodora/8.0.6/network/admin
TRACE_FILE_APPS_PROD = APPS_PROD

Error in idoc with status 20 "Error triggering EDI Subsystem"

Dear All,
I have query related to IDOC Status 20.
I am tirggering IDOC with standard t-code from IS-Retail system. I have created two ports a) TRFC port and b)File port .
<b>We are having sending and receiveing application on two different OS i.e one XI on Windows and IS Retail on AIX(Unix). I am not able to send idoc to another system. I am getting these IDOC status in WE05 (STATUS 01 , 30 , 03 , 20 )</b>
Keeping the above fatcs in mind could you please tell me how to remove the <b>error with status 20 "Error triggering EDI Subsystem".</b>

Hi prabhat,
You should have checked the automatic triggering possible at the file port level and the partner profile setting could be 'start subsytem'.
Go to WE21 and do the access test for the file port.
Once you done and find no issues then go to SM59 and test the connection for the RFC destination assigned to the ports.Possibly it has to do with the RFC destination.
Other reasons could be yours is a test client and got refreshed recently.so the production client settings might be causing this error.Check with your basis to get it working.
other reason could be the logical system assigned to the client should be having production client's name.
Check these.
I am sure you should be able to solve this issue.
Thank you.
regards,
karun.M

5 IDOC with status 29 Error in ALE service

hi there,
im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
IDOC Status Outbox:
IDOC failure between 13/07/2008 to 14/07/2009
1 IDOC with status 02 Error passing data to port
5 IDOC with status 29 Error in ALE service
IDOC Status InBox:
88 IDOC with status 51 Application document not posted
regards
raju

Hi,
Check this thread.
DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Regards.

Idoc distribution with status of error records.

Hi Gurus,
my business requirement is i want to creat the Outbound Interface to distribute the data from sapserver to ESB server using the one userdefined function module, in this custom function module i written the logic to validate the input data if validation is file those error records are updated to one return table parameter and using the FM Master_Idoc_distribute for create and distribute the sucessfull records. till its working fine (with status 30-ready to dispach, 01- idoc creatd is in we05 and i have done the all configaration of message type creation, idoc type creation, port, partnerfrofil) ,
but my requirement is , for example if in 10 records even one record is also error records then no need to distribute the idoc data to sending system, just i want to send the idoc number with status error with error message.
plese suggest me the appropriate procedure.
Thanks & Regards,
Sai Ram.

Hi,
in ur code ur filling the idoc data rcord, control record ryt ..before u append data to idoc data , u r also validating and u might be doing in loop for appening the idoc data.
if there is any error in idoc then it won't distribute the data, it will be in error status only..u can only see the data in WE02. Then u can also change the data in WE02 and redistirbute it via BD87.
if u have any conerns let me know
Regards,
Nagaraj

How to CANCEL/RESEND messages in Adapter with status system error in bulk?

Hello all,
I d like to know how can I CANCEL or RESEND messages with status error SYSTEM ERROR in adapter framework.
Messages failed because of receiver system un-availability. Now, we have more than 50.000 messages stuck, waiting for being resent or cancelled.
But from the Message Monitoring Tool at Runtime Workbench Monitoring, I can only process up to 200 messages each time.
So, its practically imposible to do it manually.
My question is how can I deal with that amount of messages? Is there a way to process them in bulk and get them cancelled in only one step/action?
Many Thanks in advance.

Hello, I hope you are doing fine!!
The most common way to cancel these messages is through the Runtime Workbench as you have mentioned youu2019ve tried.
Just one note: Once you are on the Message Monitoring screen -> Filter (where you can select the dates, message status, etcu2026), there is a Dropdown box menu at center of the screen called u201Cmaximum Numberu201D where I believe you said you can only see 200 messages.
You may try to select u201C10.000u201D there and then cancel these messages from there.
However, if you prefer doing this in one go, you can do this by changing the status of the messages from u201Cerroru201D to status u201Cdeliveredu201D by executing following SQL statement at the database level:
UPDATE <DB Schema>.XI_AF_MSG SET STATUS='DLVD' WHERE MSG_ID='<MSG ID>
AND DIRECTION='<INBOUND OUTBOUND>'
Cheers,
Jorge Eidelwein

How to create report with status killed and cancel ?

Hi Guys,
From the report query filter, i only able to pull a certain status of job ? anyone know how to pull the report for the job with status killed and cancel ?
regards,
Chris

Hi Mano,
You are in the filter editor for job definitions (Definitions > Job definitions). Job definitions do not have a status (they simply define what to do, optionally when).
Go to "Monitoring > Jobs" (First item in the first group), you can also click on the button in the tool bar. See screenshots below on my English system:
Regards,
HP

Creating Open Directory Replica fails with Server Admin Error Value 1127

Hallo,
I have seen a lot of similar threads here and they were helpful up to a certain point, but in the end, they did not solve my problem.
Currently, it comes down to this. The Server Admin Error message ist really meaningless and I could not find a single for the error value on the whole wide web. As such, I switched to the command line versions of the tools involved to geht more meaningful results. It worked. Specifically, creating a replica of an openldap master means using slapconfig.
When executing
slapconfig -createreplica master.ourdomain.com diradmin
as root on the prospective replica machine, I get the following error message:
ssh command failed with status 127
That command is not allowed with the root account via public key authentication.
That makes perfect sense to me, but how is it meant to work then?
Executing slapconfig as admin tells me that this tool is to be executed as root. On the other hand, root login via ssh is not allowed in Mac OS X by default, which seems fine to me. I even changed /etc/sshd_config on the Open Directory Master machine to "PermitRootLogin yes". However, neither reloading ssh using launchctl nor restarting the whole server made this setting operational. Trying to login from command line as root still tells me:
root login is not permitted to this machine via public key authentication.
While this is the current state where I need help urgently, I changed some other things before. I tell about to exclude these issues as possible reason of failure. I got this message for quite a while:
Replica Setup failed : This machine does not have a valid computer name
I was sure, this machine meant the target machine, the open directory master, because the domain had changed there once before I had taken over responsibility as an admin in this environment. And in fact, changeip disguised an issue there. The command proposed by changeip to fix the situation did not seem appropriate because this machine is multihomed with a public and a private IP adress. Proper name resolution is available for both interfaces including reverse lookup. I dont like this setup, but it was the only way to get mail service running smoothly. Running changeip on the machine itself using these arguments
changeip /LDAPv3/127.0.0.1 internalIP internalIP old.ours.com current.ours.com
reported success in updating password server, open directory, both interfaces, hostconfig (which in fact did not change) and samba. It reported an issue with kadmin which is related to Kerberos (we dont use Kerberos yet).
Changing the hostname of the server using changeip did not solve the issue. I then found the hint to check with scutil. This showed that the Hostname was not set on the prospective replica machine. (A question aside: in how many place is the hostname stored? The traditional /etc/hostname has gone, but seems to be replaces with several other configuration files and databases. I cant see this as an advantage). Setting the hostname using scutil worked fine. However, it did not solve the problem either. At least, slapconfig now started to complain about not being able to log in as root instead of failing from the start.
I also checked all log files on bboth machines that might have to do with openldap, as there are /var/log/slapd.log, /var/log/system.log and /Library/Log/slapconfig.log. I also checked the log of th layer on top of openldap which is /Library/Log/DirectoryService.server.log. None of them revealed anything noticeable beside a lot of of entries that I have googled in the last few hours and which all dont seem to be associated with the problem in question.
I will take a break now, but I have to fix this until tomorrow and I hope to get the ultimate hint from you, dear reader.
Thanks and bye, Christian Völker

ssh command failed with status 127
That command is not allowed with the root account via public key authentication.
Initial OD replication takes place via 'ssh'. If you have 'sshd' configured on the OD Master to authenticate with public keys then the OD replica will not be able to communicate with the OD Master via 'ssh'. You must configure the OD Master to use 'ssh' with password authentication and root login enabled.
Demote the replica back to standalone. Stop any services that you may have running on the primary network interface. Then stop any services that you may have running on the secondary network interface. In the 'Network' System Prefpane remove the IP number from the secondary interface then deactivate the secondary network interface.
Assign the private IP address and hostname that you wish to use for the replica to the primary network interface. Assign the 'public' IP number to the secondary interface. Check the DNS to see that the IP address and hostname for the primary network interface resolve both forward and reverse for the hostname of the replica that you have chosen. If it does not, fix your DNS before proceeding.
In the 'Sharing' System Prefpane, change the name of the machine to the hostname (server.domain.tld) of the replica that you have chosen. Then use 'changeip -checkhostname' to see if the IP/hostname matches. Fix it if it doesn't.
Then configure the /etc/sshd_config file on the OD master like this:
\# Authentication:
PermitRootLogin yes
PasswordAuthentication yes
PubkeyAuthentication no
and the /etc/ssh_config file on the OD replica like this:
PasswordAuthentication yes
PubkeyAuthentication no
Then from the OD replica as the 'root' user issue:
slapconfig -createreplica <ODMasterIPorFQDN> <diradmin user>
Make sure that the 'diradmin' user's password contains only alpha-numeric characters -no 'option-characters' or symbols, change it first if it does. Once the process completes, reactivate the secondary interface for the 'public' IP and check the configuration of services that will be using that IP, then start your other services. Secure the 'ssh' service on both machines to disable password authentication and 'root' logins.

Just cloned Prod to Test - adalnctl.sh: exiting with status 1

I just ran through my process to clone Prod to Test. I'm no expert but this has been done before without too many issues.
The problem I have now is when running adalnctl.sh start and I get 'adalnctl.sh: exiting with status 1'.
My configuration is 11.5.10 CU2 running in a two tier environment with forms and reports on the app tier.
Part of my process I follow is to submit some Concurrent Requests to clean-up old jobs. That's where I first noticed the job status showed as Phase=Inactive and Status=No Manager. If I check via the dashboard it shows CCM as running though.
So I decided to shut things down and restart and that where I noticed the 'apps listener' if that's the correct term as Failed.
I have run adpreclone on the Prod environment before backing up and restoring and then ran adprelcone in the Test environemt followed by adautocfg etc.
So I'll double-check to see if I've missed a step but just not sure where to start looking.
Looks like there should be a listener that tuns out of the 8.0.6 HOME?
I should mention this is on the db_tier which runs CCM and the apps_tier doesn't have this problem.
Example with the exact name edited:
Setting service OracleTNSListener80APPS_XXXX_xxxx to mode 2
Executing service control script:
/app/orafin/xxxx/xxxxcomn/admin/scripts/XXXX_xxxx/adalnctl.sh start
Timeout specified in context file: 100 second(s)
script returned:
adalnctl.sh version 115.17
Checking for FNDFS executable.
Starting listener process APPS_XXXX.
adalnctl.sh: exiting with status 1
.end std out.
.end err out.
- then later the logs shows:
[Service Control Execution Report]
The report format is:
<Service> <Script> <Status>
OracleTNSListener80APPS_XXXX_xxxx adalnctl.sh Failed
OracleConcMgrXXXX_xxxx adcmctl.sh Started
OracleReportServer-Rep60_XXXX adrepctl.sh Started
Edited by: user6445925 on Sep 21, 2010 12:34 PM

Hi;
Thanks Helios. Can I move this post or is that just and fyi for next time.Its okey :)
I did as you say and now I get 'adalnctl.sh: exiting with status 127'.Pls source env file as apps user than stop and start lsnr by using adalnctl.sh, It will give you errors again than please check log file for exact error message,
You can find log file path on my blog:
http://heliosguneserol.wordpress.com/2010/04/13/log-file-location-for-oracle-e-business-suite-r12/
http://heliosguneserol.wordpress.com/2010/04/13/log-file-location-for-oracle-e-business-suite-r11/
I think I may redo this whole process tomorrow using a FULL backup from the tonight.If your db is up and apps service running i belive you dont need to take clone again
Regard
Helios

Notifications of XI-mgs in status 'System Error - Manual Restart Possible'

Dear colleagues,
I'm using a simple communication channel of type 'GeneratedReceiverChannel_XI' in order to push XML-messages from the intergration engine into the ABAP-Backend using an ABAP server proxy. Many of these messages, however, show an error status in the XI-monitor (Notifications of XI-mgs in status 'System Error - Manual Restart Possible'). The indication of the system error is OK, since the XML-parser correctly detects a character in a field which shall be mapped to a field of type 'DEC' in the ABAP backend.
Is there any possibility to configure some type of alerting in the ABAP-backend to track especially the appearence of XML-messages in the XI-monitor with status 'System Error'?
Thanks a lot and kind regards
Stefan

HI,
As its mentioned in above postes, you can configure the Alert notification in XI which can give you the alerts about this kind of errors.
If the exception is raised after reaching to ABAP backend R/3 Side, then you may trace it in t-code SXMB_MONI of R/3.
Refer -- ALERT MANAGMENT
http://help.sap.com/saphelp_nw04/helpdata/en/3f/81023cfa699508e10000000a11402f/content.htm
Thanks
Swarup

PO status in " error In Process ".

Hi Experts,
We have some POs that are stuck in SRM with status as " Error in Process ".
The PO is got replicated to R/3.
The Workflow Log is Completed.
But in Follow-on Documents the status shows as " Error in Process ".
Can you pl. guide me int his issue.
Thanks & Regards
Sachin

Hi,
We have the same type of problem in creating invoices for our SRM 5.0 decoupled scenario.
The invoice is created and not shows any error and gives a completed message. But if we see follow-on documents it says as "Invoice -
Error in Process"
Do anybody has the same prob. solved.
Kindly suggest from gurus.
Sincerely,
Sridhar.
Message was edited by:
P.T. Sridharbabu

Report ending in warning with status 127 error

Similar Messages

Maybe you are looking for