Delete monitor logs/ IDOC

Hello
We have refreshed BW Develpoment server (3.1c) from BW production server using system copy process. Now, BW development server has the logs and IDOC of BW production server. What would be the best way to remove these logs/IDOC from the BW development server.
Thanks
Amar

dear Amar,
in the monitor, psa requests are shown,
you have to delete old psa requests,
rsa1->psa->on the root node, right click 'delete psa',
here you can determine how many days backward to be deleted. further more, you can include the psa deletion in process chain.
hope this helps.
http://help.sap.com/saphelp_bw33/helpdata/en/b0/078f3b0e8d4762e10000000a11402f/frameset.htm
Activities
Choose the PSA tree in the Administrator Workbench under Modeling.
Use the context menu for an application component, InfoSource, or a PSA Table and choose Delete PSA Data. Choose Delete on a request level.
In the following screen, the DataSources for the previously chosen application component, InfoSource, PSA table, or for the request are displayed.
Use a simple mouse click in the DataSource overview to select the DataSource for which requests need to be deleted.
To help you do this, you can display a list of the requests.
Specify the number of days or a date, that you want to use as a cutoff point. All requests before this are deleted. You also have the option to specify whether you only want to delete successfully updated requests, and/or only incorrect requests, that are no longer updated in a data target (this is only valid for transaction data).
Specify the postprocessing, if necessary.
In BW 3.0, automatic process control has been enhanced and improved significantly with the concept of process chains. Controlling the process by using postprocessing events is no longer enhanced, but continues to be supported. We recommend that you only use process chains for schedules of connected processes that must be re-defined.
Schedule the delete job.
Including the deletion of requests from the PSA in the process chain
If you want to automate the deletion of requests from the PSA, you can include an appropriate process variant in a process chain.
In the maintenance of process variants, you specify the DataSource for which the requests need to be deleted by using the implicit selection of a PSA table or an InfoPackage.
Specify the requests that need to be deleted by determining the days or dates. You also have the option to specify whether you only want to delete successfully updated requests, and/or only incorrect requests, that are no longer updated in a data target (this is only valid for transaction data).
Save your entries and go back.
In the following screen, confirm the addition of the process variants in the process chain.
You arrive in the plan view for the process chain. The process variant for deleting requests from the PSA is included in your process chain.

Similar Messages

Monitoring Log in SharePoint Foundation 2010

Hello,
I´m using SharePoint Foundation 2010 and I want to configure Monitoring log, because we have had any problems because the user changed the permissions in other sites or deleted Users.
So I want to know who makes this action in Monitoring Log SharePoint 2010.
Regards.

Take a look at this 3rd party solution:
https://auditlogsp.codeplex.com/
The Site Collection Administrator can modify audit settings, but audit settings aren't available OOTB in Foundation.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Monitoring receiver idoc communication channel

Hi All
I have an idoc to idoc scenario.
I am unable to see my receiving idoc communication channel in communication channel monitoring of RWB. It is not available in the dropdown list.
I want to have a look at the audit log to see if the idoc is delivered to the receiving system.
How can i monitor receiver idoc communication channel?
How can i ensure that the idoc is delivered to the receiving system?
In sxmb_moni, status is checkered flag.
Many Thanks
Chandra Sekhar

Hi,
IDOC is on ABAP stack hence u can not monitor IDOC.
For testing purpose
1) GO to SXMB_MONI check the status of message.
2) Go to R3 and enter Tcode WE02 and check the IDOC which is send from XI. enter the idoc name and see the status of IDOC it should be in green status if it is posted successful or else see the status record for checking the error message.
chirag

Deleting monitors with alerts configured

Iam running into an issue deleting monitors with alerts configured. It appers that a patch needs to be applied to address the issue. I logged into HP support but I dont have the entitlements under my account, and cant see the avaiable updates.

@Shawnzimm
‎Thank you for using HP Support Forum. I have brought your issue to the appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publicly post ( serial numbers and case details).
If you are unfamiliar with the Forum's private messaging please click here to learn more.
Thank you,
Omar
I Work for HP

Monitoring ALE/IDOC

Hi to all,
Can anybody please tell me some examples on monitoring ALE/IDOC.
Thanks in advance.
Regards
Monalisa

You can easily and effectively monitor inbound and outbound processing of IDocs using special reports and graphic displays. An agent can also be notified automatically using a workflow if an emergency occurs (active monitoring).
The following tools are available for monitoring:
·        IDoc Display
All the other fields of the control record are available as selection criteria as well as partners and messages
-   IDoc numbers
-   Ports
-   IDoc types
You can display a tree structure of the IDoc directly using the IDoc number. The IDoc list is displayed again if several IDocs are selected.
·        IDoc Statistics
The IDocs are sorted and represented graphically according to predefined status groups. Lists and individual IDocs can be displayed using mouse clicks.
·        IDoc Search
You can select IDocs according to their business content, that is, according to the data contained in the segments.
·         Error and Status Processing
Error and status codes are defined for the IDoc transfer. These codes can be assigned to a workflow task, which informs the agent automatically in a procedure.
The final section explains Active Monitoring.
If you receive IDocs by qRFC, this function can monitor the inbound queue and react to any errors which occur.
Prerequisites
You post inbound IDocs with qRFC.
Features
This monitoring function displays the elements in the inbound queue:
·         Display sender
·         Selected queues
·         IDoc number
·         IDoc status
·         Link to IDoc display
You can make the following changes to a queue:
·         Flag IDocs for deletion
·         Delete IDocs from the queue
·         Start a queue
Activities
Choose Tools ® IDoc Interface/ALE ® Administration ® Monitoring ® Troubleshooting ® Monitor IDoc Inbound Queue (transaction WEINQUEUE), to go to the inbound queue monitoring.
Select the IDocs or queues which you want to monitor, using the specified selection parameters.
If an IDoc in a queue has an error status, select it and go to its detail view with the Display IDoc button, to determine the cause of the error, and resolve it.
If you cannot correct an IDoc with error status, you can delete it from the queue with the Delete IDoc from Queue button.
To edit a queue, select the queue name and choose Start Queue.
If you send IDocs by qRFC, this function can monitor the outbound queue and react to any errors which occur.
Prerequisites
You send IDocs with qRFC.
Features
This monitoring function displays the elements in the outbound queue:
·         Recipient port
·         Selected queues
·         IDoc number
·         Link to IDoc display
You can make the following changes to a queue:
·         Flag IDocs for deletion
·         Delete IDocs from the queue
·         Start a queue
Activities
Choose Tools ® IDoc Interface/ALE ® Administration ® Monitoring ® Troubleshooting ® Monitor IDoc Outbound Queue (transaction WEOUTQUEUE), to go to the outbound queue monitoring.
Select the IDocs or queues which you want to monitor, using the specified selection parameters.
If queue problems occurred in transmission, you can select IDocs and go to their detail view with the Display IDoc button, to determine their status.
You can remove IDocs from the queue with the Delete IDoc from Queue button.
To send a queue, select the queue name and choose Start Queue.
In the IDoc Administration, you can assign a procedure to a workflow task error or status code.
With the Error and Status Processing function, you can check the assignment of the error procedure codes tothe standardtasks, if you have used EDI communication in an earlierversion.
You must also maintain this assignment for your user developments.
Example
Code Type ID                    Description
EDIX   2     TS0008070        ALE/EDI: Syntax error (Outgoing)
Activities
Check whether the assignment matches the table listed below.
1. Choose SAP Menu -> Tools -> IDoc Interface/ALE -> Administration -> Runtime Settings -> Error and Status Processing (transaction WE46).
2. Perform the function. The table must contain the ALE error handling entries listed below:
Code
Task
Description
Type
EDII
TS00008068
ErrorProcInb
2
EDIO
TS00007989
ErrorMessage
2
EDIP
TS60001307
idocpaket
2
EDIX
TS00008070
SynErrorOut
2
EDIY
TS00008074
SynErrorInb
2
EDIM
TS00007988
ErrorMessage
2
The table contains the assignment of the error procedure codes (e.g. EDII) forstandardtasks (e.g. TS00008068).
The procedure type is 2 (work item).
Notes
If you used EDI in an earlier version, standard tasks ofthe old versions are still assigned here for the procedure codes EDII and EDIO. If the new tasks are not entered here, there may be ALE Processing problems.
This report automatically informs the agents responsible if too many incorrect IDocs are found.
Integration
Active monitoring is not used for processing or reimporting of an incorrect IDoc. Exception handling of every incorrect IDoc is responsible for this.
Activities
You plan the report to run regularly with a variant. The variant also informs the report of the status values to be selected: If the critical status contains more IDocs than specified in the critical number of IDocs, a message is sent to a predefined recipient.
The recipient receives the notification in the form of a work item displayed in their Business Workplace. If they execute the work item, the IDoc statistics are displayed with the values determined at the time of evaluation. The agent can display the current status of these IDocs using the Refresh function. The selection criteria which led to the notification are also used for this evaluation.
An important customer orders goods using EDI on working days, between 8am and 6pm. These goods are to be delivered at 4pm the next day. To ensure that the delivery is made on time, the ordered quantity must be recorded by midday on the day of delivery. The active monitoring function is to be used at 8am every morning to determine whether there are any orders which could not be processed automatically. The report, therefore, is started at the same time every day and 0 is selected as the critical number of IDocs. The agent responsible is notified if any incorrect IDocs are found and can then manually process the outstanding orders by midday.
For more information see
Schedule Monitoring Job (example)
Schedule Monitoring Job (Example)
Prerequisites
The following refers to the example in the section Active monitoring . The active monitoring report is to be started as a background job every morning at 8am, to evaluate the IDocs which were received between 8am and 6pm on the previous day.
Procedure
Enter the RSEIDOCA report in the BAP Editor, select Variants, and choose Display.
Give your variant a name and choose Create.
Enter the following parameters:
Recipient type: US (user)
Recipient of notification, for example SMITH
Start time or End time before batch run: 1 Day and 0 Days 14:00:00h
Critical number of IDocs: 0
Status: 51 , 56 and 64
Logical message type: ORDERS
Partner parameter (here sender):
Choose Continue to enter a short text for your variant. Save your entries.
To schedule your job as a background job, choose System ® Services ® Jobs ® Job Definition and enter B (medium priority for periodic jobs) as the job class.
Select Start condition and enter a date and 08:00 as the start time.
Choose Execute job periodically.
Choose Period values ® Daily and save your entries.
Enter the scheduled report again when saving (RSEIDOCA) and the variant that you maintained.
Result
IDocs selected during the daily run of the background job will now be:
Those which were received between 8 am and 6 pm on the previous day
Those which have the logical message type ORDERS
Those received from the relevant customer
An IDoc from status 51 , 56 or 64 must be assigned now to ensure that a notification is sent to the user SMITH.
REWARD POINTS IF HELPFUL

Request without Monitor Log: APO Request or Terminated Request Generation

Hi,
While loading data to ODS from the sources system there is new error request appearing in the ODS with following description:
Request without Monitor Log: APO Request or Terminated Request Generation
Unable to see the error details as this request is not appearing in the monitor, unable to delete the request from the ODS and the error message is below.
Deletion of request REQU_435CYSN3FS0USQJXVKQOLAZ65 from data target ZRORDITM failed RSMPC 060
Deletion of request REQU_435CYSN3FS0USQJXVKQOLAZ65 from data target ZRORDITM failed RSMPC 060
Any thoughts on above issue are helpful.
Thanks
Kumar

My thoughts on this...
This problem might be caused by a program error.
DataStore objects allow you to check or generate master data ID (SID) values during the activation. If you choose to do this, the parallel processes may terminate.
<b>The following prerequisites must apply:-</b>
You activate the DataStore object data in parallel (see transaction RSODSO_SETTINGS).
During the activation, SID values are checked or generated (option "Generation of SID Values" is set).
The generated programs of the InfoObjects of the DataStore objects are not current at the start of the activation (in particular, after metadata changes).
Note 978772 - P10: Parallel SID generation terminates with deadlock
Hope it Helps
Chetan
@CP..

Managing Request without Monitor Log: APO Request or Terminated Request Gen

Hello Everyone,
Need some help of managing a system created DTP named Request without Monitor Log: APO Request or Terminated Request Generation. This is like a staging DTP provided by SAP to support data loads to DSO or Cube and, it's good if the process goes smoothly.
However when we encountered unnecessary error such as tables space or memory problem, this particular job will get stuck and there's no way to move forward or backwards from this point. There were some answers to delete the request from RSICCONT, but I don't see the direct relations here, or maybe I'm wrong.
My only question - Have anyone any idea on how to work around this.
The last thing I've in hand is to delete the whole thing (requests) and re-do from start (extraction). Not a pleasant thing as this DSO feeds to 2 Cube & 1 DSO and then to another Cube.
Thanking everyone in advance.
Regards,
Azmadi

Hi,
sad to knw you had to delete the whole data and reload. I faced the same issue today and here is what i did,
when you go to the reconstruction tab, you will find 2 ticks present
1st one that tells if request is available in data target and
2nd which gives the transfer structure status.
Now, if the first check is crossed it could mean 2 things....data no longer exists in data target or data was not updated to data target these are 2 different things.
So, in your case it wud have sed data was not updated to the target.
Solution, just reconstruct that request and then in the request tab mark it red and delete again since you dont need it.... then the activation through process chain will not fail.

Requests without Monitor Log: APO Request or Terminated Request Generation

Hello all,
Can you please help me in the following issue:
I had in an ODS, a full request of type:
Requests without Monitor Log: APO Request or Terminated Request Generation.
I deleted the request from table: RSICCONT in debugging mode. The request was on green.
Now I have problems on activating the next requests in automatically. Manually it is working.
Request REQU_6DFXRA2VWJL3KYU44JPCWKXL2 no longer exists in DSO SVO_PPAB; system is inconsistent
Activation of M records from DataStore object SVO_PPAB terminated
Please help
Thank you
Ramona

Hi,
Refer the below links,
Re: Managing Request without Monitor Log: APO Request or Terminated Request Gen
http://ar.delhigovt.nic.in/ar1/Mission%20Conv%20RFP%20-%20Vol%20I-%20V4.0.pdf
http://help.sap.com/bp_bblibrary/600/documentation/R61_BPP_EN_DE.doc
Hope it helps you,
Regards,
Ravindra.

Request without Monitor Log:

HI Frds,
When i am deleteing a req. from ODS, i am not able delete the Req. I Req. status is in Red and tech. status also in Red. Its showing DTP/Infopackage as "Request without Monitor Log: APO Request or Terminated Request Generation" and not able to see the Moniter(RSMO).
Kindly can one give me some solution to delete these type req. ?
Thanks
Pari

Hi,
Apply the recommendation of the above note:
1138410-->execute the report RSSM_ZOMBIE_REQUEST_DELETE before checking if you do not have entries in the table RSSELDONE or the table RSMONMESS but which may be displayed in the administration of a
data target with the descriptive text "Request without monitor log: APO request or terminated request creation".
I hope it helps.
Best regards,
Fran.

Acs:Delete specific log for user X

Hi Experts
on the acs 5.2 , how to delete specific log for user X, ?
thanks
jamil

Not sure if this answers the question you are asking but the following option is available:
Monitoring Configuration > System Configuration > Collection Filters
Pres "Create" and Syslog Attribute of "User" and set the user name your are interested in
This option prevents records for this user from being collected. It does not remove any records that have already been collected

How to delete old logs in SAP BI, what is the best way to go?

Hi,
below are the issues we are facing,
when executing infopackage job is not getting triggred into source system.
for activation DSO data it is taking huge time. At the time of seqential read to RSREQDONE table.
I think this is due to huge logs in the staandard tables.
What could be the reson behind this.. and let me know how to delete old logs.
Thanks,
Harish

Hi,
just carry out RSRV for DSO PSA tables and see if there is inconsistency available there in the PSA table.
see if the change log and PSA deletion is happening regularly..else schedule same in PC
check with basis there are certain jobs which needs to run regularly at certain frequency..
http://www.erphowtos.com/guides-a-tutorials/doc_view/1041-how-to-delete-process-chain-logs-in-sap-bw.html
http://www.erphowtos.com/guides-a-tutorials/doc_view/1040-periodic-maintenance-activities-on-sap-bw-best-practices.html
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a02ba9e7-bb6f-2c10-09b4-e86b9fcbad41?QuickLink=index&overridelayout=true
Thanks and regards
Kiran

GRC:AC:SPM: How to ensure SAP_ALL in not deleting FF log files?

Hi Guys,
Due to some critical business requirements occuring occasionally, I wanted to set up a FF ID having SAP_ALL. This would be besides the other FF IDs, which I have already created for each of the modules. I.e basically this SAP_ALL FFID would be to handle emengency and cross module tasks.
Now, I have a limitation here that this FFID having SAP_ALL profile may do anything and then even clear all the logs for what all it did (as it would have unlimited access to even delete the logs for FFID usage). Any workaround solution for this?
Regards.
Hersh.
http://www.linkedin.com/in/hersh13

Zaheer is exactly correct. The main point of SAP_ALL is to be (almost) unrestricted and that is why it is recommended to not assign it.
Although Firefighter allows you to gain elevated access in a controlled manner, if you just assign firefighter ID's SAP_ALL then you will be allowing that access in the systems effectively, invalidating any controls which you had there previously.
There are loads of ways of trimming SAP_ALL but I would generate a role based on the SAP_ALL template and de-activate the key authorisations (GRCFF_0001).
Simon

Communication channel monitoring logs

Dear all,
on weekend we had a problem with a CC. Messages not have beend pick up from
a FTP server. The problem was solved automatically and I was not able to see
any error entries in the CC monitoring log files because there were to many
entries without error.
My question:
Is there an option for persisting the logs into a trace file on server? I was not
able to find the entries in defaultTrace or anywhere else.
How to raise the time/size of the log files?
Thanks
Chris

Hi,
I think the channel was getting locked and so, it could not pick up any data.
Refer the SAP note 849089 for this.
-Supriya.

Monitoring of IDOC

Hello all,
I try tu have a good monitoring of IDOC.
To be clear, I will explain the problem.
We use the IDOC HRMD_ABA for the replication sap HR towards an other system CRM.
Sometimes we have some IDOC not in error but not fully posted status 52 (via transaction BD87).
The problem is : the message is not fully clear I don't know on which segment I got the error. I would like to add more information to the message, I look on customer function but I found no appropriate function => I told me why not to copy the function module [IDOC_INPUT_HRMD] for the IDOC's post into a [ZIDOC_INPUT_HRMD] function module and to manage better the message error but it looks a heavy work.
Anybody has a better idea to realise that ?
I try also to read the table EDIDS and EDID4 but the information was not helpfull.
Thank you very much in advance, Gene.

Hi Genevieve,
Yes there is a better (and much easier) way.
Go to the customer exit 002 for this specific function.
Function module = EXIT_SAPLRHA0_002.
Inside you will find: INCLUDE ZXHALU06 .
Double click on ZXHALU06 (and if it does not exist, create it by answering Yes on the create dialog).
Then simply use your coding to investigate the results and/or extend the message.
This customer exit is meant for monitoring workflow functions for this IDoc handler.
However, to copy IDOC_INPUT_HRMD to your own ZIDOC_INPUT_HRMD and extend this is not so very much work. You only need to find out with which partner the communication occurs (e.q. EDIDC-SNDPRN field).
Find this partner in transaction WE20. Indise the transaction find the message in the inbound parameters.
Double-click the partner and go to the Process code field.
Double-click the process code field and you will see that with the identification the function module IDOC_INPUT_HRMD is given.
Press the button behind the identification field and remember all fields from that screen.
Once you have copied to ZIDOC_INPUT_HRMD you can replace the identification with your function module and fill in the related fields (that you did remember).
Hope this gives you a good start.
Regards,
Rob.

How to delete archive log files from ASM through Grid Control

Hi
Anybody suggest me how to delete archive log files from ASM through Grid Control.
Thanks

It is important to specify both, the oracle version and os version when posting, so confusions can be avoided.
In this particular case, since you are referring to asm and grid control you could be talking about either 10gR1, 10gR2 or 11gR1; but I strongly suggest you to avoid us to be guessing. In either case, you sould go to the maintenance tab of the target database and program a scheduled 'delete noprompt obsolete;' procedure. This will purge the information stored at the Flash recovery area, which I assume you have declared inside the ASM.
~ Madrid
http://hrivera99.blogspot.com/

Delete monitor logs/ IDOC

Similar Messages

Maybe you are looking for