Archiving/Deleting - Changing msg status

Hello Everybody
I've configuring archiving on my XIP system. Old messages are flagged as "TO BE DELETED" because they weren't in "Define interfaces for archiving ...." !!!
I'd like to know if I can change this flag to "TO BE ARCHIVED" directly in  SXMSPMAST. Are there any other tables I need to do something?
Thanks
Julio

Hi Julio,
no, this has to be tagged in SXMB_ADM per interface in "Interfaces for archiving and persist duration" before you send any messages for the required interfaces. All message sent before can only be deleted.
With standard functions from SAP there is no possibility!
Possibly the direct change in the table is ok, but I have no experience with it.
From my point of knowledge it should be only this table!
regards
Dirk

Similar Messages

  • Delete shoppingcarts with status approved or change status

    Since the backend system was updated with the latest support packages a lot of SC didn't pass anymore and got stuck in the system.
    sers have reorderd most of them but now the old sc remain. as soon as I pass the fix which caused the problems  the old sc's will be passed since the sollution will also apply to these sc's .So I was looking for a way to change the status or delete the items.
    I found
    how to delete a approved shopping cart
    Delete shopping cart
    In the monitor I can't get to the shoppingcarts anymore since they are approved. So I was curious how I can delete the line items if I can't access the sc anymore.  ??
    we work with SRM 5.5
    kind regards
    arthur

    I try to block the shoppingcarts with the function
    BBP_PD_SC_STATUS_CHANGE
    but every status I try it gives the error that the status is not allowed or there are follow up documents.
    Which status can I use to block/delete/lock approved shoppingcarts which contain errors (but don't after implementation of the corrections)
    I tried AM05 AM12 DELE DMLL
    kind regards
    arthur
    Edited by: A. de Smidt on Oct 28, 2010 2:49 PM

  • Archive/delete table SXMSPMAST with MSGSTATE = 1 or 23

    Hi experts,
    In table SXMSPMAST how to change the Message Status(MSGSTATE) 1 & 23 to 3?
    Because Archive/delete job is not cleaning messages from table SXMSPMAST with Message Status(MSGSTATE) = 1 & 23.
    I already tried using RSWF_XI_UNUSED_MSGS.
    Regards

    Hi,
    Here are a few tips on how to delete messages, and also enable messages for deletion which are not in final state.
    To release messages in unarchivable statuses: http://host:port/MessagingSystem/archiving/reorgdb.jsp
    Schedule following reports weekly (depending on your error handling and reporting procedures for your system this might not be possible in your production system):
    RSXMB_CANCEL_MESSAGES
    RSXMB_CANCEL_NO_COMMIT_MSG
    RSXMB_CANCEL_NOT_REST_MESSAGES
    RSXMB_CHECK_ITFACTION
    RSWF_XI_INSTANCES_DELETE
    SXMS_REFRESH_ADAPTER_STATUS
    In addition you have the following reports dealing with enabling messages for archiving deletion
    u2022     RSWI_REGENERATE_WI2OBJ (uncheck u201CDisplay modeu201D and set for relevant dates)
    u2022     SXMS_REFRESH_ADAPTER_STATUS -     Success: all msg with adapter status 001 changed to 006 (archivable)
    u2022     RSWF_XI_UNUSED_MSGS (recommended not to run in production to avoid loosing data)
    RSXMB_SHOW_REORG_STATUS shows number of messages scheduled for archiving/deletion
    RSXMB_SHOW_STATUS shows number of messages per message status, and adapter status for messages with message status = 003 (Processed successfully)
    RSXMB_CHECK_MSG_QUEUE fixes inconsistencies by changing the message statuses 001, 009, 012 and 016 to 014/021.
    Hope this helps!
    Br,
    Kenneth

  • PI 7.1 Archiving - Delete

    hi Team,
    We have PI 7.1 production environment and planning to implement ARCHIVING & DELETE for Integration Engine, Adapter Engine and Business Process Engine based messages.
    I had referred to 'How to arhive & delete' doc that highly available in SDN but few question after going through the doc.
    1. If a interface flagged for ARCHIVING then all messages in complete message status gets automatically Archived
    2. And if interface not flagged for ARCHIVING then all messages of those interfaces gets automatically Deleted
    Ofcourse on these both the cases, the corresponding action takes place only provided the retention period candition meets.
    1. But Wondering, How about the messages that NOT successfully processed? Somewhere in SDN i red the NOT completetly proccessed messages require to be first 'Cancelled' and then they get marked for ARCH so that it gets archived! So in this case, both 'Synchronous" and "Asynchronous" not completely proccessed messages have to be marked for 'Cancel' before they get Archived?
    2. Keeping this aside how the not completely processed archving, Why we need to archive the messages that are not completely proccessed in PRODUCTION environment?
    3. In regards to 'NOT Completely processed' messages, I agree to certain extend that "All these have to be removed" from Database so that we gain disk space that helps improve the performance also? Please share your knowledge.
    4. Either Archiving or Delete mechanism has any dependance or functional variations on Synchronous and Asysnchronous?
    I highly appriciate all those add their knowledge here to clarify
    Regards
    Sekhar

    Dear Sekhar,
    let me go through your questions step by step...
    1. But Wondering, How about the messages that NOT successfully processed? Somewhere in SDN i red the NOT completetly proccessed messages require to be first 'Cancelled' and then they get marked for ARCH so that it gets archived! So in this case, both 'Synchronous" and "Asynchronous" not completely proccessed messages have to be marked for 'Cancel' before they get Archived?
    This is almost correct. Canceling is required for asynchonous messages in error state only. By canceling a message its state changes from error to final and this it is allowed to be archived. In contrast synchronous messages are final right when processing fails.
    Please note: archiving applies to asynchronous messages only. It is a general decision by SAP to not archive synchronous messages.
    2. Keeping this aside how the not completely processed archving, Why we need to archive the messages that are not completely proccessed in PRODUCTION environment?
    Once an asynchronous message enters the central Intergation Server(IS) or the local Integration Engine(IE) XI/PI takes over responsibility for this message. Canceling a message means a serious violation of the EO/EOIO protocol. This violation needs to be documented in productive environments for the purpose of tracebility.
    3. In regards to 'NOT Completely processed' messages, I agree to certain extend that "All these have to be removed" from Database so that we gain disk space that helps improve the performance also? Please share your knowledge.
    I am not quite sure that I got the point. For each message entering the IS/IE SAP has to provide a guided procedure to reorganize this message. For successfully processed messages this is done by standard house-keeping jobs for archivng and deletion. For messages in error state there are basically two ooptions:
    (1) restert message after error has been fixed;
         -   if message processing is sucessful this time, we are back to normal
         -   if message processing fails again, we are in the very same siutation as before
    (2) cancel messages; this males the message 'final' and then it is treated like sucessfully processed messages.
    Thus, this is all about defining an end point in the lifecycle of each message.

  • XI Messages Archive & Delete

    Please help regarding messages archive & del. our xi production disk is almost full. i went through many threads regarding this , also OSS note: Note 872388. but nothing is working for me. would somebody please tell me the steps in simple & clear to do the acrh & del. I am posting the reports RSXMB_SHOW_STATUS & RSXMB_SHOW_REORG_STATUS in the next post.
    Thanks

    RSXMB_SHOW_STATUS
    ====================
    Table Container:                                   SXMSPMAST
    Overview
    ========
    Time Stamp Not Included
    Number of Messages in Database:                                           1,890,176
    Number of Messages in Client:                                             1,890,176
    Number of Messages for Reorganization in Client:                          1,890,176
    Number of Messages to Be Archived in Client:                                    834
    Number of Logically Deleted Messages in Client:                                   0
    Number of Archived and Logically Deleted Messages in Client:                      0
    Message Status
    ==============
    Message Status:      001 Number:                  0
    Message Status:      002 Number:                  0
    Message Status:      003 Number:          1,888,648
    Message Status:      004 Number:                  0
    Message Status:      005 Number:                  0
    Message Status:      006 Number:                  0
    Message Status:      007 Number:                  0
    Message Status:      008 Number:                  0
    Message Status:      009 Number:                  0
    Message Status:      010 Number:                  0
    Message Status:      011 Number:                  0
    Message Status:      012 Number:                  0
    Message Status:      013 Number:                  0
    Message Status:      014 Number:                950
    Message Status:      015 Number:                  0
    Message Status:      016 Number:                  0
    Message Status:      017 Number:                  0
    Message Status:      018 Number:                 11
    Message Status:      019 Number:                  0
    Message Status:      020 Number:                  0
    Message Status:      021 Number:                567
    Message Status:      022 Number:                  0
    Message Status:      023 Number:                  0
    Message Status:      024 Number:                  0
    Message Status:      025 Number:                  0
    Message Status:      026 Number:                  0
    Message Status:      027 Number:                  0
    Message Status:      028 Number:                  0
    Message Status:      029 Number:                  0
    Message Status:      030 Number:                  0
    Message Status:      030 Number:                  0
    Adapter Status
    ==============
    Adapter Status of Messages with Message Status:              003
    Adapter Status:      001 Number:                 49
    Adapter Status:      002 Number:                  0
    Adapter Status:      003 Number:                  0
    Adapter Status:      004 Number:                  0
    Adapter Status:      005 Number:                  0
    Adapter Status:      006 Number:          1,888,105
    Adapter Status:      007 Number:                271
    Adapter Status:      008 Number:                  0
    Adapter Status:      009 Number:                  0
    Adapter Status:      010 Number:                  0
    Adapter Status >     010 Number:                  0
    RSXMB_SHOW_REORG_STATUS
    ===========================
    Overview     
    =========
    Retention periods and message and adapter status ignored in the following
    Number of messages in DB:       1,890,024
    Number of messages in client:    1,890,024
    Number of messages in client still to be reorganized:      1,890,024
    Archiving
    ============
    Number of messages to be flagged for archiving
    Message and adapter status is ignored in the following
    - Msgs not in retention period (can be archived):            0
    - Msgs in retention period (cannot be archived):           688
    Message and adapter status is considered in the following
    - Messages to be flagged for archiving:          0
    Number of messages already flagged for archiving
    - Messages to be archived:            0
    Number of archived messages that can now be deleted
    - Messages to be deleted:          0
    Delete
    =======
    Number of messages to be flagged for deletion
    Message and adapter status is ignored in the following
    - Asynchr. msgs not in retention period (can be deleted):   1,888,303
    - Asynchr. msgs in retention period (cannot be deleted):        1,033
    Message and adapter status is considered in the following
    - Asynchronous messages without errors to be flagged:              0
    Message and adapter status is ignored in the following
    - Synchr. msgs not in retention period (can be deleted):           0
    - Synchr. msgs in retention period (cannot be deleted):            0
    Message and adapter status is considered in the following
    - Synchronous messages without errors to be flagged:              0
    - Synchronous messages with errors to be flagged:                0
    Number of messages already flagged for deletion
    - Messages to be deleted:          0

  • HOT backup done but archives deleted after end backup, so need backup from

    Hello Team,
    I did HOT CLONE upto sequence :-
    alter database begin backup; and golbal change#=12564
    alter database end backup ; and sequence#=12675
    Now the problem is my archives are deleted between 12564 and 12675,
    I want to take backup for the sequences deleted from production, How can i do??

    No, It's not possible.
    Datafiles contains the data being thrown into the database from its inception (first use of the Database itself). That too, the data is scattered inside the datafiles, so you couldn't guess that based upon time when they're filled up i.e. it's not like one data file will be used first and other one next...based upon the factors like how your tablespaces are defined etc...Data will be scattered.
    As someone answered, try to copy archives from production (OS level copy) and recover the Database here.
    PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
    Thanks,
    CSM

  • Error in CV02N while changing the status.

    Hi Experts,
    We are getting a error while changing the status of technical change document that " Inconsistent characteristic value assignment" .The document is in status "in use" and we are trying to change it to " old version" using T code CV02N.
    when I tried to see the error desription it is telling that delete the inconsistencies. But I didn't find the list of incosistencies. What may be the problem? Please help me out to get ride of this problem.
    Thanks and best regards,
    Praveen

    Hi Pete,
    The full text message: Inconsistent characteristic value assignment
    Message no. C1821
    In diagnosis it is telling that "You want to change the value assigned to a characteristic. However, the change causes inconsistency, so the new value is not allowed."
    Actually I am just changing the status of the document. I am not changing any characteristic value.
    Actually it is appearing as information message. but while saving it pop up and not allowing to save.
    Please do the needful.
    Best Regards,
    Praveen

  • Change Msg partner in support desk message

    Hi,
    I want to change the msg processor in support desk message from webdynpro. Which RFC Function module will be helpful ?
    Note : with the following function module we already tried , it is not changing msg processor in solution manager Sup dsk.
    crm_order_maintain
    crm_order_save
    bapi_transaction_commit
    Please refer the following code.
    FUNCTION zchange_msgpart.
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(OBJECT_ID) TYPE  CRMT_OBJECT_ID OPTIONAL
    *"     VALUE(IT_LINES) TYPE  COMT_TEXT_LINES_T OPTIONAL
    *"     VALUE(I_STATUS) TYPE  CRM_J_STATUS OPTIONAL
    *"     VALUE(REF_PARTNER_NO) TYPE  COMT_PARTNER_NUMBER OPTIONAL
    *"     VALUE(PARTNER_NO) TYPE  CRMT_PARTNER_NO OPTIONAL
    *"  EXPORTING
    *"     VALUE(ET_EXCEPTION) TYPE  CRMT_EXCEPTION_T
    *"  TABLES
    *"      RETURN_N STRUCTURE  BAPIRET2 OPTIONAL
    Import Parameters for CRM_ORDER_MAINTAIN
      DATA :  lt_status  TYPE crmt_status_comt,
              lt_text    TYPE crmt_text_comt,
              lt_partner TYPE crmt_partner_comt,
              lt_billing TYPE crmt_billing_comt.
    changing Parameters for CRM_ORDER_MAINTAIN
    Local fields for CRM_ORDER_MAINTAIN
      DATA: lv_guid TYPE crmt_object_guid,
      lt_object_to_save TYPE crmt_object_guid_tab,
      ls_input_fields TYPE crmt_input_field,
      ls_status TYPE crmt_status_com,
      ls_field_names TYPE crmt_input_field_names,
      lt_field_names TYPE crmt_input_field_names_tab,
      it_partner TYPE crmt_partner_comt,
      ls_partner TYPE crmt_partner_com,
      lt_input_fields TYPE crmt_input_field_tab,
      l_logkey TYPE crmt_logical_key,
      ls_temp_input_fields TYPE crmt_input_field_tab,
      ls_billing TYPE crmt_billing_com,
      lt_saved_object TYPE  crmt_return_objects,
      ls_text TYPE crmt_text_com.
    Get the GUID for the Transanction no
      SELECT SINGLE guid
                    INTO lv_guid
                    FROM crmd_orderadm_h
                    WHERE object_id = object_id.
      CHECK sy-subrc EQ 0.
      ls_text-ref_guid = lv_guid.
      ls_text-ref_kind = 'A'.
      ls_text-tdid     = 'SU01'.
      ls_text-tdspras  = sy-langu.
      ls_text-tdstyle  = 'SYSTEM'.
      ls_text-tdform   = 'SYSTEM'.
      ls_text-mode     = 'A'.
      APPEND LINES OF it_lines TO ls_text-lines.
      APPEND ls_text TO lt_text.
      APPEND lv_guid TO lt_object_to_save.
      ls_status-ref_guid = lv_guid.
      ls_status-ref_kind = 'A'.
      ls_status-status = i_status.
      ls_status-user_stat_proc = 'ZENT0001'.   "MODIFIED BY SRINIVASULU
      ls_status-activate = 'X'.
      APPEND ls_status TO lt_status.
      ls_input_fields-ref_guid = lv_guid.
      ls_input_fields-ref_kind = 'A'.
      ls_input_fields-objectname = 'STATUS'.
    CONCATENATE ls_status-status  ls_status-user_stat_proc INTO l_logkey.
      DATA: lf_guidset TYPE crmt_object_guid.
      DATA: lf_par_guid TYPE comt_partner_guid.
      SELECT SINGLE guid_set FROM crmd_link INTO lf_guidset WHERE guid_hi = lv_guid AND objtype_set = '07'.
      SELECT SINGLE partner_guid FROM crmd_partner INTO lf_par_guid WHERE guid = lf_guidset.
    for message processor
      ls_partner-ref_guid           = lv_guid.
      ls_partner-ref_partner_no     = ref_partner_no.
      ls_partner-ref_partner_fct    = 'SDSM0004'.
      ls_partner-ref_no_type        = 'BP'.
      ls_partner-ref_display_type   = 'BP'.
      ls_partner-partner_guid       = lf_par_guid.
      ls_partner-ref_kind           = 'A'.
      ls_partner-ref_partner_handle = '0000'.
      ls_partner-kind_of_entry      = 'C'.
      ls_partner-partner_fct        = 'SDSM0004' .
      ls_partner-partner_no         = partner_no.
      ls_partner-display_type       = 'BP'.
      ls_partner-no_type            = 'BP'.
      ls_partner-mainpartner        = 'X'.
      APPEND ls_partner TO it_partner.
      ls_input_fields-ref_guid = lv_guid.
      ls_input_fields-ref_kind = 'A'.
      ls_input_fields-objectname = 'PARTNER'.
      CONCATENATE ls_partner-ref_partner_handle ls_partner-ref_partner_fct ls_partner-ref_partner_no
                  ls_partner-ref_no_type ls_partner-ref_display_type INTO ls_input_fields-logical_key.
      ls_field_names-fieldname = 'DISPLAY_TYPE'.
      APPEND ls_field_names TO lt_field_names.
      ls_field_names-fieldname = 'NO_TYPE'.
      APPEND ls_field_names TO lt_field_names.
      ls_field_names-fieldname = 'PARTNER_NO'.
      APPEND ls_field_names TO lt_field_names.
      APPEND LINES OF lt_field_names TO ls_input_fields-field_names.
      APPEND ls_input_fields TO lt_input_fields.
      CLEAR : ls_input_fields,lt_field_names[].
      MOVE l_logkey TO ls_input_fields-logical_key.
    ls_field_names-fieldname = 'ACTIVATE'.
      CLEAR : ls_field_names,
              lt_field_names[],
              ls_input_fields,
              ls_temp_input_fields[] .
      CALL FUNCTION 'CRM_ORDER_MAINTAIN'
       EXPORTING
          it_text                       = lt_text
      IT_SCHEDLIN_I                 =
          it_partner                    = it_partner
          it_status                     = lt_status
          it_billing                    = lt_billing
        CHANGING
          ct_input_fields               = lt_input_fields
       EXCEPTIONS
         error_occurred                = 1
         document_locked               = 2
         no_change_allowed             = 3
         no_authority                  = 4
         OTHERS                        = 5
      IF sy-subrc <> 0.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
               WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    CALL FUNCTION 'ZCRM_ORDER_SAVE'
      EXPORTING
        it_objects_to_save         =  lt_object_to_save
       IV_UPDATE_TASK_LOCAL       = '-'
       IV_SAVE_FRAME_LOG          = TRUE
       IV_NO_BDOC_SEND            = TRUE
    IMPORTING
       ET_SAVED_OBJECTS           = lt_saved_object
       ET_EXCEPTION               = et_exception
      ET_OBJECTS_NOT_SAVED       =
    CHANGING
      CV_LOG_HANDLE              =
    EXCEPTIONS
       DOCUMENT_NOT_SAVED         = 1
       OTHERS                     = 2
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    ENDFUNCTION.
    prakash

    Hi Jijo,
    a better solution may be to create a custom partner function called Main Message Processor and assign it to SLFN. I'm not sure how to flag one as the main any other way.
    regards,
    Jason

  • How to change the status of a production order

    Dear All,
    May i know how to change the status of a production order.I want to de-active the status like OPGN (Operation generated).This status is updated as there was no routing assigned to that particular production order during its creation
    Thanks and Regards,
    Varun Siddharth

    Dear,
    When you create a production order, an operation created by the system is generated automatically if no routing is used for the creation. As a result the order header receives the status HOGAN; the operation created automatically also has this status.
    If you delete the operation created automatically and then do not have the status HOGAN.
    To avoid this maintain the Routing for the material or delete the setting of default operation from OPJG.
    Regards,
    R.Brahmankar

  • Changing the status of appraisal document

    dear experts,
    I am working in ECC 6.0
    I have created an appraisal category and template and want to maintain it for evaluations and released the document
    After saving and completing the document, i want to revoke the status from "released " to "non released". I have also deleted all the appraisals thro " transaction -"appchange "
    i am not able to revoke the status from released to non released . what is the solution for this issue ?
    early reply solicited
    nataraj s

    Hi
    You will not be able to change the templates that have been released. This is a part of the standard functionality.
    To unrelease and make the changes execute the following steps
    1. Go to transaction phap_admin
    2. Delete all the open documents (in process, assigned, etc) corresponding to the appraisal template
    3. Right click the appraisal template in phap_catalog and change the status to not release
    Judith

  • How to change the status of updated record?

    Hi All,
    how to change the status of updated record?
    new record should be active version(X) and old version will be deleted.
    Plz suggest..
    Thanks in advance...

    Steve,
    In the actual question, you mentioned that the old record needs to be deleted and hence the solution provided.
    Now, you are talking about field. May I know which field are you talking about??
    Jst get in to ABAP Editor and try debugging the code with the solution provided and let us know if that is working fine or not.
    Also, I recommend you to take a look at the transaction ABAPDOCU. There you wil find hell lot of examples explaining all the scenarios. You will get a good idea .
    Please check that and try to implement it yourself. You will be able to make it after doing mistakes.
    If you stuck up again after many attempts, paste your code here. We will help you out
    Hope you got my concern.
    Thanks,
    Babu Kilari

  • Issue with Archiving & Deletion of messages in PI ,SXMB_MONI messages

    Hello experts
    I am  working on Archiving & Deletion of messages in PI ,SXMB_MONI, i have fallowed all the steps which are avialable in /people/deepak.shah/blog/2010/04/22/archiving-deletion-of-messages-in-pi--part-2, but the messages still there in SXMB_MONI.
    please help me to resolve this issue.
    regards
    chandra

    Hi Krish
    i have fallowed steps like....
    in SXMB_ADM
    >>>step 1: Define the interface for archivng and retnetion period
    >>>step2):Schedule Archive Jobs,
    after this i have checked the in SM37 the jobs got sheduled and released after that it showing finished.
    >>>step3):ARV_BC_XMB_WRP<date> (archiving, step 1)
    ARV_BC_XMB_DEL<date> (archiving, step 2)
    here i am getting message like "0 XML messages got archived".
    "0 XML message for deleated".
    I have doubt in SXMBPMAST  table here when i check the status of interface , ITFACTION field is containing the value INIT and if I understood correctly it job deletes only those messages where ITFACTION is set to DEL.
    We are actually trying to delete the messages avoiding archiving but what I am seeing is we cannot delete error messages and for them we must have to go through archiving. Please correct me if I am wrong.
    Thanks
    Chandra

  • How to get the old and new statuses of CAD indicator (DRAW-CADKZ) while changing the status of document (DRAW-DOKST)?

    I want to delete the originals of document while changing the status of document based on CAD indicator status. For this I have implemented BADI DOCUMENT_STATUS01 and the method AFTER_CHANGE_STATUS. From this, the BADI is triggering whenever I am changing the document status and I can able to delete the originals. But here my requirement is to check the CAD indicator status to delete those originals. I.e. whenever the document status will change first time the CAD indicator status will also change. Based on that old and new status of CAD indicator I have to do delete operation.
    If anybody has an idea about SAP documents please help me
    Thank you,
    Regards,
    Ramesh

    First the document is exists in SAP in FR status. But when the CAD system will connect to SAP then the status is changing from ‘FR’ to ‘IN’ after that the CAD Indicator is populating from Blank to ‘X’.
    I want to know in which place the CAD indicator value is changing (any user exits available or any BADI s available when changing the CAD indicator) when connected to CAD system.

  • LSMW for changing user status on work order(IW32)

    Hi All,
    I have created a LSMW for changing user status on work order using transaction IW32. It does not change the status when i run the LSMW. In the recording for the LSMW, i select the radio button on the user status i want to select.
    When i run the LSMW in the foreground, it does everything except select the correct status.
    Is there a way to fix this or is it a problem with LSMW. I'm using ECC6
    Kind Regards
    Emanuel

    Hi ,
    I am not sure whether it would work with LSMW but if your on ECC 6.00 ,Enhacement Pack 3 then you have BADIs which allow you to make collective status changes in IW38 .The below are those BADIs :-
    BADI_EAM_RIAUFK20_FCODE_CUS1 :Implement Customer Function Code in Order List
    BADI_EAM_RIAUFK20_FCODE_SAP1 :Implement SAP Function Code in Order List
    Else if your on lower version then write up a batch programme which checks the PM Order types with specific status and sets user status using FM STATUS_CHANGE_EXTERN[This is used to set or delete User Status] in SE37 ..
    regrds
    pushpa

  • Archival/Deletion of messages in XI 3.0 SP23

    Dear All,
      We need to carry out a data deletion/purging activity at our XI box, where no archival/deletion policy has been incorporated ever. As a preparatory measure, I need to have some guidelines for the activities as under,
    1. While defining an Archival policy, is there any recomendation from SAP or others that message archival exercise has to be carried out first, before proceeding with message deletion? To be more precise, can we directly delete/purge the messages without archiving them? What will be the impact of such an exercise on the XI system?
      This point may sound confusing but the reality is that we do not have enough H/W to carry out an activity of Archival and Deletion.
    2. What is the SAP recomendation/best practice in this regard?
    3. Although we are defining the Archival/Deletion policy now, we need to purge data that is 3 years old and we do not require them any more. What would be the best practice to carryout this activity?
    Thanks and regards,
    Sugata Basu

    Hi Sugatada,
    is there any recomendation from SAP or others that message archival exercise has to be carried out first, before proceeding with message deletion?
          No as per my knowledge..
    can we directly delete/purge the messages without archiving them? What will be the impact of such an exercise on the XI system?
         This wholly depends on requirement...if the data is too old...you can directly delete it..no need to archieve..
    What is the SAP recomendation/best practice in this regard?
      you can set these values which close to best practice...
    Retention period for both synch and asynch
    msgs without error awaiting deletion : 180 days
    msgs without error awaiting archieving : 45 days
    retention period for history entris for deleted msgs : 30 days
    in XI we have 2 types of action:
    (1) deletion of XML messages (without prior archiving)
    (2) archiving of XML messages with subsequent deletion
    SAP_BC_XMB_DELETE* for type (1)
    SAP_BC_XMB_ARCHIVE* for type (2)
    Regds,
    Pinangshuk.

Maybe you are looking for