Application Log Issue

Hello all,
I need to get the application log data into an internal table.
I have the following parameters with me: 1) OBJECT ID
2) SUBOBJECT
3) EXTERNAL ID
When i enter the same in SLG1 i get the information.
How do i get the entire message into an Internal table in my program.I n
Regards,
Arun

Hello Arun,
Using function module 'APPL_LOG_READ_DB' u can read the application log.
DATA: P_NUMBER_OF_LOGS LIKE SY-TABIX.
Log header data
DATA: BEGIN OF P_HEADER_DATA_TAB OCCURS 0.
INCLUDE STRUCTURE BALHDR.
DATA: END OF P_HEADER_DATA_TAB.
Log parameters
DATA: BEGIN OF P_HEADER_PARA_TAB OCCURS 0.
INCLUDE STRUCTURE BALHDRP.
DATA: END OF P_HEADER_PARA_TAB.
Log messages
DATA: BEGIN OF P_MESSAGE_TAB OCCURS 0.
INCLUDE STRUCTURE BALM.
DATA: END OF P_MESSAGE_TAB.
Message parameters
DATA: BEGIN OF P_MESSAGE_PARA_TAB OCCURS 0.
INCLUDE STRUCTURE BALMP.
DATA: END OF P_MESSAGE_PARA_TAB.
CALL FUNCTION 'APPL_LOG_READ_DB'
EXPORTING
    OBJECT          = 'ZTEST'
    SUBOBJECT       = 'ZTEST01'
    EXTERNAL_NUMBER = 'Application Log Demo'
IMPORTING
    NUMBER_OF_LOGS = P_NUMBER_OF_LOGS
TABLES
    HEADER_DATA        = P_HEADER_DATA_TAB
    HEADER_PARAMETERS = P_HEADER_PARA_TAB
    MESSAGES           = P_MESSAGE_TAB
    MESSAGE_PARAMETERS = P_MESSAGE_PARA_TAB.
Please let me know any help needed further.

Similar Messages

Deleting expired application logs is key to improving mass activity performance issues

During mass activity runs reference is made to the system's application logs during the process of line item selection. Performance based issues can be overcome by deleting old/expired application logs from the system, and rebuilding the affected table index. Based on my analysis on these issues, there has been a significant observation of 90% improvement in performance.

Dear Astrid,
Depending on the performance trace observed using transaction ST12, if for instance the SELECT on a particular table takes the most time, deleting all expired application logs and rebuilding the table index will result in a significant performance improvement.
Yes 90% improvement will be observed across the entire mass activity run. In my example below I use table BALHDR.
1. Run report SBAL_DELETE to delete all expired
application logs from table BALHDR
    1.1. At the selection screen of report
SBAL_DELETE, set the radio button for the expiry date to 'Only logs which have
reached their expiry date’
    1.2. Under the tab for 'Selection
conditions', enter the affected transaction code. e.g FPVA
    1.3. To delete the entries, set the radio
button under the Options tab to 'Delete immediately'
    1.4. Finally, execute or use shortcut F8 to
delete logs
2. Rebuild index 1 on table BALHDR (create a
secondary index on the table).
I hope this helps.
Kind Regards,
Adrian

Performance Issue with application logs

Hi
Has any one come across or aware how to address a issue in Event Management on R/3 as well as SCM side where the application log tables (BALDAT) are loaded causing peformance issue to the system?I have checked the SAP notes in this connection but its not of any help.Any event change is causes lot of logs registration.
Thanks in advance
Anders.

Hello Anders,
on R/3 side you can disable logs in transaction /SAPTRX/ASC0AO on AO Type and Event type level.
In the EM/SCM system you have per Event Handler Type options to control the log in transaction /SAPTRX/TSC0TT.
Logs for Event Messages can be disabled in transaction /SAPTRX/TSC0MBF.
Recommendation is that you disable all logging in big production environments and only enable it when you have any problems.
Best regards,
Steffen

Issue regarding application log in standard program RPCLMSU0

System Status: SAP ECC6, SP15.
This probem has been observed after we have upgraded from 4.6C.
In the include RPCLMSUF of the Report RPCLMSU0, there is an FM BAL_LOG_MSG_ADD, which adds messages to an application log.
A structure is passed to the FM, of type bal_s_msg.
The first 3 components of the structure are of type:
sy-msgt, sy-msgid and sy-msgno.
These should normally be filled in by values from the FM called just above it: BAL_LOG_CREATE.
But this doesnu2019t happen.
So, SAP has hardcoded values for these 3 as u2018Eu2019 (Message type), HRPAYNA_ALV (Message ID) and u2018998u2019 (Message no).
These are the values that get printed when the program is tested. i.e. the hardcoded text is getting displayed.
Output in the ALV : HRPAYNA_ALV:998 ***********No records found***********
We have checked the documentation for the FMs, and even gone through a few sample programs that SAP has created like SBAL_DEMO_02. The output is perfect here.
Since this is code that SAP has added (Entire form added "SL0K008292) by SAP to its standard code, they must believe that these hardcoded text will still not get printed. Can this error can be corrected by making some configuration changes in the system (SLG1?).
The code of the suroutine where this FM is called is given below:
FORM alv_appl_msg_add USING iv_text1 TYPE any
                            iv_text2 TYPE any
                            iv_text3 TYPE any
                            iv_text4 TYPE any.
Constants delcation.....
CONSTANTS: lc_msgid TYPE sy-msgid VALUE 'HRPAYNA_ALV', " Message ID
             lc_msgty TYPE sy-msgty VALUE 'E'. " Message Type
Data declarations.....
DATA ls_msglog TYPE bal_s_msg.      " Structure for msg log
ls_msglog-msgty     = lc_msgty.
ls_msglog-msgid     = lc_msgid.
ls_msglog-msgno     = gv_msgno.
ls_msglog-msgv1     = iv_text1.
ls_msglog-msgv2     = iv_text2.
ls_msglog-msgv3     = iv_text3.
ls_msglog-msgv4     = iv_text4.
Function module is used to add the messages to message log
CALL FUNCTION 'BAL_LOG_MSG_ADD'
    EXPORTING
      i_s_msg = ls_msglog
    EXCEPTIONS
      OTHERS = 1.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.                               " IF sy-subrc <> 0
ENDFORM.                               " alv_appl_msg_add

Hi
Pass IDoc Number, Date, Time from EDIDC table to FM-
'APPL_LOG_READ_DB'.
You'll get all log details of that IDoc.
For only Message, check FM - 'IDOC_GET_MESSAGE_ATTRIBUTE'.
Regards.

Log4j and sunone application server8.1 logging issue

Hi,
Im using log4j's getLogger to generate application logs in sunone application server 8.
Following is the error generated in server.log under sunone application server8.1:
[#|2005-09-28T21:49:47.725+0800|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=17;|2521125 [httpWorkerThread-59185-6] INFO CI_APPS - DBAdapter|Initialised RegistryService:sg.gov.moe.regservice.RegistryService@61e987
|#]
[#|2005-09-28T21:49:47.776+0800|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=17;|2521196 [httpWorkerThread-59185-6] INFO CI_APPS - DBAdapter|Initialised Context
|#]
[#|2005-09-28T21:49:47.776+0800|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=17;|2521196 [httpWorkerThread-59185-6] INFO CI_APPS - DBAdapter|Looked up datasource
|#]
[#|2005-09-28T21:49:47.916+0800|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=17;|2521336 [httpWorkerThread-59185-6] INFO CI_APPS - queryDB|qrySQL:select username, name, role, rights, email, pdo from CI_ADMIN_user where username = 'S1234567G'
|#]
It is successfully logged to the application log as well as expected.
Anyone knows how can I resolve the err from being generated in server.log?
thanks!

Hello, it is possible to generate logs in a different location, other than server.log. The domain.xml has a log-service element, that contains a log-handler attribute, which allows this. Thanks.
The other option is for the application to attach a handler to the javax.enterprise.system.stream.err logger. For doing this, the application code must have permission. This can be granted by adding an entry to the server.policy file.Thanks.

Log messages for 'auditing' are different in 'general' and'application log

Hi,
From UI, When I audit a file using a profile which comprises of user-defined 'rules/categories/analyzers', I will get log messages at ''File-name(Application) log window' and 'Messages' log window, which are located at bottom of Jdev UI page. One common message in both the log windows is
" <n1> violations, <n2> exceptions, <n3> documents, <n4> seconds>.
But here the 'n1,n2,...' numbers are dfferent in two windows though the log output is for a same file. In this the 'file-name' log shows the correct
Example:-
In 'file-name' log window ,it shows as:
3 documents, 8 violations, no exceptions
In messages window, it shows as
"Audit starting on EFC.jpr (Default)
Audit completed: no violations, no exceptions, 3 documents, 1 second"
If I use the 'pre-existed'(Jdev's) rules profile, I will get similar output in both log windows.
From this I concluded that there is something missing to register for a new 'rule/category/analyzer'.
Could you suggest me in this case. Do I forgot anything to do in any files of '<rule-implementation.java>', 'audit.properties', <add-in launcher>.java, extension.xml.
Actually, I want to use 'ojaudit' executable from command line to my project files. Here I observed that the output of the 'ojaudit' is similar to the above explained 'Message' log window in JDeveloper UI. But where the 'Message' log window output is not correct for user-defined rules.
Regards
Madhu

Romano,
In the upcoming production release (planned to be released next week), we added caching of authorized roles and permissions in JhsAuthorizationProxy class.
I suggest you wait for this relase, if the problem persists, it is most likely an ADF issue (as is the logging)
Steven Davelaar,
JHeadstart team.

Regarding Sun Java System Application Server Issue with JVM

Regarding Sun Java System Application Server Issue with JVM
Hi
I have installed SJSAS9.1 on solaris system. I m trying to deploy war file which i compiled in windows enviorment by jdk1.5.0_05. Every time i got the following error :
type Exception report
message
descriptionThe server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP
PWC6199: Generated servlet error:
[javac] javac: invalid target release: 1.5
[javac] Usage: javac
[javac] where possible options include:
[javac] -g Generate all debugging info
[javac] -g:none Generate no debugging info
[javac] -g:{lines,vars,source} Generate only some debugging info
[javac] -nowarn Generate no warnings
[javac] -verbose Output messages about what the compiler is doing
[javac] -deprecation Output source locations where deprecated APIs are used
[javac] -classpath Specify where to find user class files
[javac] -sourcepath Specify where to find input source files
[javac] -bootclasspath Override location of bootstrap class files
[javac] -extdirs Override location of installed extensions
[javac] -d Specify where to place generated class files
[javac] -encoding Specify character encoding used by source files
[javac] -source Provide source compatibility with specified release
[javac] -target Generate class files for specific VM version
[javac] -help Print a synopsis of standard options
note The full stack traces of the exception and its root causes are available in the Sun Java System Application Server 9.1 logs.
I have cheked jvm version on both system the only difference is :
Solaris points to jdk 1.5.0_09
Windows point to jdk1.5.0_05
Even i tried to run blank jsp also but again i got the same error.
Can any help me to sort out the problem or give me any idea so i can do something by my own.
Thanks in Advance
Gagan

Do you have ANT installed and available?
Thanks,
Kedar

Doubt in creating program to display application logs

Hi,
I have doubt in creating a program to display application logs.
The standard transaction code SLG1 has been used to display Application logs till now by the user.
They came up with the new requirement on this.
<u>The requirements were:</u>
1)New custom program shoud be created like SLG1 with limited selection fields( data from, date to, Program name and User)
2) Detail list should be displyed immediately when this program is executed because SLG1 gives Basic list,Detailed list which is getting displayed when 'Detail view' is selected in the first list.
I have created one program with limited selection fields as per the requirement using the below function modules .
BAL_FILTER_CREATE
BAL_DB_SEARCH
BAL_DB_LOAD
and BAL_DSP_LOG_DISPLAY
<u>Issue :</u> still I am getting the firt list.
both Basic and Detailled lists are getting triggered at the FM BAL_DSP_LOG_DISPLAY.
Is it only the way to copy and modify this FM.
Could you please suggest me?
Thans in advace,
babu.
Message was edited by:
        babu v
Message was edited by:
        babu v

Hello All,
Thanks for your valuable suggitions.
I have seen most of the demo programs.
I found one fm'BAL_DSP_PROFILE_NO_TREE_GET' which avoids the tree list which is getting listed above the profile list.
I have been searching alot to omit the Profile list. I searched alot to find any function modules realted to that.
The requirement was only the Detail list should only be listed.
Could you please suggest me to avopid that profile list also?
Thanks in advance,
babu
Message was edited by:
        babu v

Warning message into Application log of Service request

Hi Experts,
I have a requirement where I am using Event handlers(CRMV_EVENT) to redetermine partners of a service request whenever certain values are changed in the transaction CRMD_ORDER.
Partners will be retrieved from a custom table.
In any circumstances, if the partners cannot be determined then we need to push a WARNING message stating that "Partners can not be determined, pls maintain the values in the custom table'.
For this purpose I am using the function module CRM_MESSAGE_COLLECT with the following parameters, but still I am not able to see the same into the Application log of the Service request that is going to be created.
CALL FUNCTION 'CRM_MESSAGE_COLLECT'
EXPORTING
    iv_caller_name         = 'ORDERADM_H'
    IV_REF_OBJECT          = iv_header_guid
    IV_REF_KIND            = 'A'
   IV_LOGICAL_KEY         = '0001'
    IV_MSGNO               = '001'
    IV_MSGID               = 'ZSP'
    IV_MSGTY               = 'W'
IV_MSGV1               = SY-MSGV1
IV_MSGV2               = SY-MSGV2
IV_MSGV3               = SY-MSGV3
IV_MSGV4               = SY-MSGV4
    IV_MSGLEVEL            = '1'
IV_FIELDNAME           =
IV_ACTION              =
    IV_LOG_HANDLE          = lv_log_handle
    IV_CUMULATE            = 'X'
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Do I missed in passing of any additional parameters?
Can any one of you have encountered the same problem and solved this, pls through some light on me too(if possible with block of code).
Thanks in advance.

Hi,
Here is the block of code that I used to push a message in to Application log.
Push your message into a variable called dummy and then call the below mentioned function module.
DATA:        lv_dummy(254)    TYPE c,            "#EC NEEDED
          MESSAGE w052(sppf_media) WITH text-001
                                        text-002
                                    INTO lv_dummy.
          CALL FUNCTION 'CRM_MESSAGE_COLLECT'
            EXPORTING
              iv_caller_name = 'ORDERADM_H'
              iv_ref_object = iv_header_guid
              iv_ref_kind    = lc_ref_kind_a
              iv_msgno       = sy-msgno
              iv_msgid       = sy-msgid
              iv_msgty       = sy-msgty
              iv_cumulate    = lc_x
            IMPORTING
              ev_msgty       = lv_msgtyp
              es_msg_handle = gv_msghandle
            EXCEPTIONS
              not_found      = 1
              appl_log_error = 2
              OTHERS         = 3.
          IF sy-subrc <> 0.
            MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                   WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
          ENDIF.
        ENDIF.
Hope this helps to resolve your issue.
Regards,
Usha.

XI 7.0 NW 2004s install - JMS Errors in applications.log & defaultTrace

We just installed XI 7.0 NW 2004s. The installation of XI 7.0 NW 2004s is a lot simpler than XI 3.0 NW 2004 since the Template installer runs most of the post installation steps.
However, there are a few issues that I am encountering that i did not see with XI 3.0 installations. The installation is on Windows 2003 server and SQL server 2005.
Checking the applications.log file through Visual Administrator LogViewer, I see that the Applications log is filing up every few seconds with the following repeating errors:
Message -
Exception on server occured! Internal error.
Additional Information -
Category : /Applications/JMS
Message ID : 001422B146E800750000070D0000013000041A845FCB659B
Source Name : /Applications/JMS
Thread : SAPEngine_Application_Thread[impl:3]_26
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d16ec30026fd11dbb450001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : com.sap.jms.client.session.Session
Resource Bundlename :
Session : 0
Source : /Applications/JMS
ThreadObject : SAPEngine_Application_Thread[impl:3]_26
Transaction :
User : J2EE_GUEST
Message -
Exception on server occured! Cannot write to transaction log TXf48.tx.
Additional Information -
Category : /Applications/JMS
Message ID : 001422B146E800750000070A0000013000041A845FCB4CC8
Source Name : /Applications/JMS
Thread : SAPEngine_Application_Thread[impl:3]_26
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d16ec30026fd11dbb450001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : com.sap.jms.client.session.Session
Resource Bundlename :
Session : 0
Source : /Applications/JMS
ThreadObject : SAPEngine_Application_Thread[impl:3]_26
Transaction :
User : J2EE_GUEST
In the defaultTrace.trc file, i see the JMS error too:
Message -
Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:1808)
     at com.sap.jms.client.session.Session.rollback(Session.java:300)
     at com.sap.jms.client.session.Session.close(Session.java:158)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:262)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:361)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Additional Information -
Category : /Version
Message ID : 001422B146E8008B000007340000013000041A847A0F6CB9
Source Name : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession
Thread : SAPEngine_Application_Thread[impl:3]_98
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d815880126fe11db9edc001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : /Version
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession
ThreadObject : SAPEngine_Application_Thread[impl:3]_98
Transaction :
User : J2EE_GUEST
This is filing up both the applications.log and defaultTrace files. I cannot find any information through Service Marketplace. Has anyone encountered this issue? This is new installation - no messages are running on it so I am not sure why there is a JMS error.
Regards,
Jay

Hi Jay,
The exception means that the JMS Provider is not able to write to the transaction log file upon close of a transacted session. In NW04s, JMS transactions are stored as files on the local file system. The location of the root folder where the transactions are persisted is configured by the JMS service property "transactionStorePath". You can check its value through the Visual Administrator -> Services-> JMS Provider -> Properties. Please check if it contains a correct directory path and that nothing prevents the server from writing to this path - access rights, enough disk space, etc. If there is something wrong with the path, you can change it, save the change and restart the JMS provider service for the change to become effective.
You can also have a closer look at the server trace file: the root cause of the above exception is some other exception, probably I/O one, and it should be logged somewhere in adjacency to the JMS exception.
There is ongoing JMS communication even in a new server installation - in this case (judging from the stack trace) the component that performs this JMS activity is the timeout service.
Hope this helps,
Stoyan

Application messages are in the system log instead of the application log

Hi SAP GURUS.
The standard output is created from the outbound delivery .
All the messages are hitting the system log instead of the application log .
This is after the upgrade from 4.6c to ECC 6.0 .
Please provide the details how to move the log to the application log since the output is the standard output (SAP provided output type ).

verzunof wrote:
Hello,
My system.log is filled with these messages, they repeat every second.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Do these messages indicate a problem? If so what that could be problem and the solution?
Can this contribute to the sleep/wakeup problem when iMac won't wakeup after being put to sleep manually and not sleeping according to Power Saving settings?
Thanks a lot.
verzunof wrote:
I'm not certain if those messages indicate a power issue but you can try *resetting the System Management Controller* and see if that helps. Here's how: http://support.apple.com/kb/HT1806
"The System Management Controller (SMC) is a chip on the logic board that controls all power functions for your computer. If your computer is experiencing any power issue, resetting the SMC may resolve it. The SMC controls several functions, including:
Telling the computer when to turn on, turn off, sleep, wake, idle, and so forth.
Handling system resets from various commands.
Controlling the fans."
Carolyn

Log entries in Service Consupmtion Layer Application Logs of Duet Enterpr

Dear all,
I need your inputs to solve the below mentioned issue,
There is a communication developed between MS sharepoint and SAP.
By using Mapper Classes for each and every operations the conversion of data format from Sharepoint to SAP and viceversa happens.
We can see the message or error logs created during the conversion process using the T-code /iwfnd/view_log.
But i want my custumized messages has to come in that log for that i used the following code in the mapper class Post method but still my logs are not coming in the T-code /iwfnd/view_log.
DATA: lo_logger TYPE REF TO /iwfnd/cl_logger,"logger singleton
lo_message_container TYPE REF TO /iwfnd/if_message_container,"message container
lv_message TYPE bapi_msg,
lv_log_material TYPE symsgv,
lv_log_plant TYPE symsgv,
lv_instance_counter TYPE i,
lv_previous_pur_doc TYPE char10.
CONSTANTS gc_log_agent_name TYPE /iwfnd/sup_iw_agent VALUE 'Dev Guide Purchase Req'.
CONSTANTS gc_log_msg_id TYPE symsgid VALUE 'ZDUET_SCL_PR'.
Get logger
CALL METHOD /iwfnd/cl_logger=>get_logger
RECEIVING
ro_logger = lo_logger.
initialize the post mapper log step
lo_logger->log_step_init(
EXPORTING iv_msg_number = 000 "Post Mapping started for Purchase Req Header Query
iv_msg_id = gc_log_msg_id " message class
iv_system_alias = iv_system_alias "Backend System Alias
iv_agent = gc_log_agent_name "Dev Guide Purchase Req
RECEIVING
rv_msg_handle = lv_msg_handle ).
lo_logger->log_message(
EXPORTING
iv_msg_type = /iwfnd/cl_logger=>info " Message Type
iv_msg_id = gc_log_msg_id " Message Class
iv_msg_number = 006 " Message Number
iv_msg_v1 = lv_instance_counter " Message Variable
iv_system_alias = iv_system_alias " System Alias
iv_agent = gc_log_agent_name " IW Agent
Else
read through the input parameters for logging query parameters
READ TABLE it_parameters INTO ls_parameters WITH KEY attr_name = 'MATERIAL'.
lv_log_material = ls_parameters-low.
READ TABLE it_parameters INTO ls_parameters WITH KEY attr_name = 'PLANT'.
lv_log_plant = ls_parameters-low.
get the message container to add messages
lo_message_container = io_request_data->get_message_container( ).
set the request result code to failed so a fault message can be created
CALL METHOD io_request_data->set_result_code
EXPORTING
iv_result_code = /iwfnd/if_srd_request_context=>cs_result_code-failed_permanent.
add the message to the message container, this will create an error log entry automatically
CALL METHOD lo_message_container->add_message
EXPORTING
is_object_key = ls_key
iv_msg_type = 'E' "Error
iv_msg_id = gc_log_msg_id
iv_msg_number = 004 "Query for Material &1 and Plant &2 returned no results.
iv_msg_v1 = lv_log_material
iv_msg_v2 = lv_log_plant
iv_is_leading_message = abap_true
iv_message_creator = gc_log_agent_name.
Endif.
end this post mapper log step
lo_logger->log_step_completion( EXPORTING
iv_msg_type = /iwfnd/cl_logger=>info
iv_msg_id = gc_log_msg_id
iv_msg_number = 002 "Post Mapping finished for Purchase Req Header Query
iv_system_alias = iv_system_alias
iv_agent = gc_log_agent_name
iv_msg_handle = lv_msg_handle ).
please let me know the answe for this issue.
Many thanks in Advance,
Harish

Hi Girimurugan,
I am currently working with SAP Gateway related stuffs and I need a clarification regarding the application log.
Hope you are very busy and please clarify the doubts if you can spare few minutes towards this query.
Appreciate your valuable advise towards this.
Query:
Can we log any of the different types of logs (I Info / W Warning / A Abort or Cancel / E Error ) into Application Log(/IWFND/APPS_LOG) of the Gateway system in a Hub deployment model ?
How the logging can be achieved?
What are the scenarios, wherein the Application logs are preferred?
Also I have already raised a query in the SCN with this link: http://scn.sap.com/message/15477543. But could not get much details about it.
Can you please clarify the same?
Thanks & Regards,
Mohamed Meeran

EM Application Log and Web Access Log growing too large on Redwood Server

Hi,
We have a storage space issue on our Redwood SAP CPS Orcale servers and have found that the two log files above are the main culprits for this. These files are continually updated and I need to know what these are and if they can be purged or reduced down in size.
They have been in existence since the system has been installed and I have tried to access them but they are too large. I have also tried taking the cluster group offline to see if the file stops being updated but the file continues to be updated.
Please could anyone shed any light on this and what can be done to resolve it?
Thanks in advance for any help.
Jason

Hi David,
The file names are:
em-application.log and web access.log
The File path is:
D:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_brsapprdbmp01.britvic.BSDDRINKS.NET_SAPCPSPR\log
Redwood/CPS version is 6.0.2.7
Thanks for your help.
Kind Regards,
Jason

Transaction for application log

Using IDOCS. One has errored but cannot get into application log as pop up not appearing (memory issue or something) for me to double click the log number and go into the application log to view it. Does anyone know the transaction or menu path to access the application log direct so I can see what the error is about?
Many thanks
Larissa

Hi,
USE SLG1 Transaction.
Thanks,
Naga

How to Write Error messages to application.log file in OAS 10g.

Hi All i am in urgent need of writing log messages to Oracle Application Server10g application.log file.
Using JDeveloper 10.1.3.4.0.4270.
Thanks & Regards,
Renuka
Edited by: Renuka on Jan 18, 2013 8:00 AM

Zariel wrote:Boot from where? If you want the entire boot process you can use debug parameter. BUT I dont know what you will get becauseyour harddrive gets mounted during init, and during init it dumps dmesg to a log file, i guess dmesg gets its logs from minilogd which also gets started during init. The only way of doing it would be to get the kernel to log its output to ram then flush it to disk at the relevant time. Ive no idea if you can do this or not.
I just boot normally from my hard disk, but all the messages between "INIT version 2.86 booting" and the output from /etc/issue (when login is started), is gone. It's not in /var/log/messages nor do I get it via dmsg.
All the kernel messages BEFORE "INIT version 2.86 booting" are logged okay.

Application Log Issue

Similar Messages

Maybe you are looking for