Reset/undo a transport

Hi,
Is it possible to reset/undo a transport?
I have a transport in Dev. containing activation of some business content. Unfortunatly this activation, activated some already used objects (already in production), they have now been reset to the business content version(!) The list of modified objects is long, and therefor I hope for some "smart" way of undoing the changes in the transport. Rollback of the entire transport would be perfect, but unforunatly not possible. So, is the only way of reseting theses objects the "hard" way, the manual way? Or?
The transport is not released from development.
Thanks.
BR
AH

Hi AH,
Unfortunately you cant revert those changes in BI  as you do in ABAP.
go through the link below
Re: How to revert the changes in SAP BI based on a particular user and date
Also two extreeme ways our reverse transport, ie QA to dev.. but rarely will any landscape have such connections established. consult with your basis if this possible and the amount of effort needed..
Also there is a risk of loosing recent developments to those objects that were not yet moved to quality...
There is one more method, but it will wipe of all other peoples developments as well..
COPYBACK from QA to DEV .
I think, you would be better of comparing those objects and manually reverting the changes.
Regards,
Sunmit.

Similar Messages

  • How can I reset/undo a movement stabilized clip?

    Hello everybody,
    My question is regarding the dominant movement stabilization that Final Cut Pro X can do. It's very clever, but sometimes does more harm than good, the clips turn into funhouse funhouse mirrors. I believe it's doing its best with my shaky footage, but I can't figure out how to undo a stabilization of a given clip, or reset it – does anyone know how this can be done?
    On non-stabilized clip I have the option to Analyse and Stabilize, as well as a Stabilization item in the Inspector. Here I can customize it manually.
    But on a clip already stabilized via Analyze and Stabilize there is no Stabilization item in the inspector, and no mention that the clip has already been stabilized. It's a bit too Microsoft for my taste ('I know what's best for you') if I have to accept the application's fix.
    Of course I could reimport the media all over and not have it stabilize it, but this clip is already edited on my Timeline.
    Any input appreciated - thanks!
    Thomas

    Just some images for illustration.
    Inspector for non-stabilized clip:
    Inspector for stabilized clip (via Analyze and Stabilize) – no stabilization item:
    And the contextual menu option Analyze and Stabilize on a non-stabilized clip, any mention of stabilization is gone on an already stabilized clip ...

  • Reset/undo the Deletion Indicator in the Prod Orders

    Hi Friends,
       I have set the Deletion Flag and feletion Indictor inthe Prodcution orders in order to prepare them for Archiving. Now I want change some of them.
    But I am unable to go into Change mode of Prod Orders(CO02). Message says Prod Order is already deleted and hence can only be displayed.
    How can I reset the deletion Indicator?
    Thanks
    Siva

    Thanks Diego!! I can reset the Deletion Flag  from CO02 but not the deletion Indicator which I set vis the program PPARCHP1. Now I am even unable to go to CO02.
    Siva

  • How to undo an order of transport which has returned an error code 8

    Hi experts,
    While transporting an installation of business content, it has removed a lot of transfert rules. Could you tell me how to undo this transport from quality to the production envirenenmet. Unfortunately I dident check the transport order which has returned the code error 8.
    Thank you for your answer.
    Regards.

    Hi Joseph,
    Transport all the objects you want in the order again with a new request. This will replace all the transported objects and you will get all the objects transported.
    Regards,
    KK.

  • Transport request released -undo is possible

    I have released unnecessary tranport request into QA system.Is thier any way we can undo the transport release request and save the objects in QA system.
    Issue is -I have captured transport request using transport connection .it capture all the unnecassary objects and i didn't noticied and i have released the request.
    Is their any way I can undo the  released transport request.
    Please advise on this.

    You can do if you have not given as over written while importing it.. You can contacct Basis guy or if you have permissions check in SMTS T-code.
    I am not sure about your landscape, even you have released basis guy can do Import.. generally...But if you have done import with overwritten option.. we canoot rollback.
    Explain me
    1. Will the import happens automatically
    2. or Basis guy will do
    3. r u doing the import..
    If its automatically overwritten, then we cannot do anything .. but for remainig we have options
    Ananya

  • How can i delete a transport request?

    Hello:
    I only speak a little english. I wait that you can understand me.
    I have a transport request that is released. I make bad this request and i need delete it. But, when i go to se10 and I try to delete I recive this messagge:
    Request/task ____ already releaded (not modificable).
    How can I delete this request?
    Thank you very much.
    Report RDDIT076 is internal and should not be executed by customers.
    - Reported by Jason ORiordan
    Message was edited by: Suhas Saha

    Hi,
    It is easilly possible to delete the cofile and the datafile of the released transport request but why would you need to do that ?
    It is also possible to delete a transport request in the transport tables but it is a very bad idea and could even be seen as a temptative to hide a forbidden action in the system.
    It will be seen by a security audit as this would create a hole in the request order numbering.
    You would need to use direct database access to delete a released transport request.
    As I told you before, I would NOT do it as it is hasardous et may generate security audit problems.
    You can also destroy your transport system.
    Transport requests are stored in table E070.
    We only modify the e070 table after system copy by database refresh to reset the next transport request number. It is done by inserting a line in the table. We never delete inside this table.
    Use at your own risk !
    Regards,
    Raj.

  • Is it possible to delete a released transport

    Hello
    I wander is it possible to delete a released transport request. Is it possible to delete a transport request with released only an task

    Hi Tina,
    You would need to use direct database access to delete a released transport request.
    As I told you before, I would NOT do it as it is hasardous et may generate security audit problems.
    You can also destroy your transport system.
    Transport requests are stored in table E070.
    We only modify the e070 table after system copy by database refresh to reset the next transport request number. It is done by inserting a line in the table. We never delete inside this table.
    Use at your own risk !
    Regards,
    Olivier

  • Trouble connecting debugger to local process

    I'm using JDeveloper 10.1.3.1.0 on WinXP SP2 with Java 1.5, running a JSF/EJB 3.0 application on the embedded OC4J server. About 90% of the time, I try to start the debugger on a JSF/JSP file, and JDeveloper is unable to connect the debugger. I tried selecting a Debugger Port Range of 4000 - 4999, but this doesn't seem to make any difference.
    Here's the output when the debugger fails to connect:
    [EJB 3.0]: Assigning default-data-source=jdbc/SmashExpressDS, specified in projects EJB 3.0 properties
    [Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
    C:\install.dsk\jdevstudiobase10131\jdev\system\oracle.j2ee.10.1.3.39.14\embedded-oc4j\config>
    "C:\Program Files\Java\jdk1.5.0_06\bin\javaw.exe" -client -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=4000 -classpath C:\install.dsk\jdevstudiobase10131\j2ee\home\oc4j.jar;C:\install.dsk\jdevstudiobase10131\jdev\lib\jdev-oc4j-embedded.jar -Xverify:none -DcheckForUpdates=adminClientOnly -Doracle.application.environment=development -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config C:\install.dsk\jdevstudiobase10131\jdev\system\oracle.j2ee.10.1.3.39.14\embedded-oc4j\config\server.xml
    [waiting for the server to complete its initialization...]
    Listening for transport dt_socket at address: 4000
    ERROR: transport error 202: recv failed during handshake: Connection reset by peer ["transport.c",L41]
    JDWP exit error JVMTI_ERROR_NONE(0): could not connect, timeout or fatal errorProcess exited with exit code 0.
    Debugger unable to connect to local process.
    Thanks in advance for any help.
    Rick

    Me too. Running on fresh Fedora Core 6 Linux and jdev 10131 and jdk1.5.0_09. Until recently I ran on SuSE 10.1 with 1013 and had no problems. I've added "AddVMOption -Djava.net.preferIPv4Stack=true" to jdev.conf to avoid ipv6 problems and disabled firewall and selinux. Watta f is dis? Problem is narrowed down to plain "hello world"... Error looks like:
    /home/local/java/jdk1.5.0_09/bin/java -hotspot -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=4004 -classpath /home/jms/Documents/Projects/FileShare/Client/classes no.jmsconsult.fileshare.client.file.DirectoryClimber
    Listening for transport dt_socket at address: 4004
    Debugger unable to connect to local process.
    Message was edited by:
    jonmarti

  • Error Creating Flexible Planning (MC93)

    Hi I am implementing Flexible Planning and I have had problems changing characteristics in info structures.
    1. First in Development environment I customized an info structure that i transport to QAS.
    2. I deleted a characteristic in the info structure I generate again the tables and everything it´s ok and I execute transaction MCSY for resetting, then i transport to QAS and I don´t have problems.
    3. The problem it´s when I add a new characteristic to the info structure I execute the same steps and I transport to QAS when I try to create a Planning (MC93) I got an error: "Internal error : 047 in routine Planning Coding" Message No. MA 098
    I was looking for notes and there is the same error but in older versions and all the support packages have been implemented. I am using 4.6c version and I found this problem in older versions like 3.0 I really don´t know what it´s going on and i hope you could help me or maybe what could be the reason. I don´t think that it´s customizing.
    Thank´s in advanced

    HI, I proved like this:
    1. I executed transaction MC8O for regenerating programs.
    2. I executed transaction MC22 for generate info structure
    3. I created a new transport order
    4. I realesed the transport order
    5. The transport was made from Development to QA
    Again I got the following transport errors:
    "Finished with return code 8" = 8 errors
    I proved again with transaction MC93 for create a new Flexible Planning and I´ve got error 047 again.
    What do you suggest???

  • Quicktime won't play on Safari on Apple Troubleshoot page. Firefox OK.

    When I go here on Safari:
    http://www.apple.com/quicktime/troubleshooting/
    I do not get a Quicktime Logo. When I go there on FIrefox, I get the logo. I can play the Apple trailers on Safari. I have a problem with some streaming (RTSP) sites elsewhere (on safari not firefox).
    I am on 10.6.2 with ALL updates. Safari is 4.0.4 (6531.21.10). Firefox is 3.5.8. I am on a MacPro4,1.
    SL won't let me install QT7.
    Any ideas on how to debug this?

    I reinstalled QT7 from the install disk and rebooted but the problem still occurs.
    Above response was to get QT 7 to install -- not to fix QT RTSP which, in my opinion is non-functional at this time under Snow Leopard. Basically, the "logo" you see on the "Troubleshooting" test page is just the animated "buffering" logo. If you want to see what the real spiraling "animated logo" looks like, then view the same test page under Tiger or Leopard OS.
    About the only other thing you can currently do is reset the RTSP "transport" settings but this did not fix things on my system:
    If you're using QuickTime X on Mac OS X Snow Leopard:
    1. Quit QuickTime Player if it's running. Open the Terminal application which is located in the Utilities folder.  
    2. Cut and paste the following command into the command prompt and press the Return key: 
qtdefaults reset TransportSettings
    3. You should see the following message displayed in the Terminal window:
"Quicktime has been configured to automatically determine the best protocol and port for streaming."
    4. Quit the Terminal application.

  • COPA Delta Mechanism

    Hi All,
    Can any one explain about Delta Mechanism in COPA ie.,
    How delta works in COPA,
    From where the delta record are picked,
    When the Delta Queue is filled,
    what is Safety Delta,
    What is Relignment and when we go for that, etc.....
    Thanks in Advance,
    Regards
    Ramakrishna Kamurthy

    Hi Ramakrishana,
    Up to and including Plug-In Release PI2003.1, a DataSource is only
    defined in the current client of the R/3 System. This means that a
    DataSource can only be extracted from this client. The DataSource has a
    timestamp for the delta method, and this timestamp is only valid for th
    current client. This timestamp is managed by Profitability Analysis.
    With Plug-In Release PI2004.1 (Release 4.0 and higher), timestamp
    management was converted to a new method, called generic delta. This
    method works in connection with an SAP BW system with Release 2.0 and
    higher. With this method, timestamp management is no longer performed b
    Profitability Analysis, but instead by the Service API (interface on th
    R/3 side between Profitability Analysis and SAP BW). Exclusively in
    Release 3.1I, Profitability Analysis continues to support timestamp
    management.
    Compared to timestamp management in Profitability Analysis, the generic
    delta allows for several enhancements:
    o   You can apply the delta method simultaneously using the same
         DataSource from more than one R/3 System client because a separate
         timestamp is saved for each logical system.
    o   You can apply the delta method for the same R/3 System client
         simultaneously using the same DataSource from several SAP BW
         systems.
    o   You can perform several initializations of the delta method with
         different selections using the same DataSource from a given SAP BW
         system for the same R/3 System client.
    o   The DataSource commands the Delta Init Simulation mode. With
         timestamp management in Profitability Analysis, this mode had to be
          implemented using the Simulate Delta Method Initialization function
          (see SAP Note 408366).
      For more information on the generic delta, see Delta Transfer, whereby
      the steps of the Specify Generic Delta for a DataSource section are
      performed automatically for Profitability Analysis when a DataSource is
      created. For this, the field determining the delta is taken as the
      timestamp for Profitability Analysis (TIMESTMP), and the timestamp is
      stored for summarization levels and line item tables. However, in
      contrast to generic DataSources, the TIMESTMP field is not generated in
      the extraction structure because this is not necessary for DataSources
      in Profitability Analysis. As with timestamp management in Profitabilit
      Analysis, an upper limit of 30 minutes is set as the safety interval.
      You find the timestamp of a DataSource for the delta method in the
      current logical system either in the Header Information for the
      DataSource using the IMG activity Display Detailed Information on
      DataSource or using the IMG activity Check Delta Queue in the Extractor
      IMG. The timestamp is shown here when you choose the selection button i
      the Status column for the combination of DataSource and SAP BW system.
      DataSources created after implementing PI2004.1 automatically apply the
      new method. DataSources that were created in Plug-In releases prior to
      PI2004.1 still continue to use timestamp management in Profitability
      Analysis but can be converted to the generic delta. For this, an
      additional selection option Convert to Generic Delta appears in the
      selection screen of the IMG activity Create Transaction Data DataSource
      when a DataSource with timestamp management in Profitability Analysis i
      entered. Conversion from the generic delta to timestamp management in
      Profitability Analysis is not supported.
      Conversion is only possible for DataSources that are defined in the
      current client of the R/3 system and for which the delta method has
      already been successfully initialized or for which a delta update has
      successfully been performed. This is the case once the DataSource has
      the replication status Update successful. Furthermore, no realignments
      should have been performed since the last delta update.
    For the conversion, the timestamp for the current R/3 System client is
    transferred from Profitability Analysis into the timestamp of the
    generic delta. In this way, the transition is seamless, enabling you to
    continue to perform delta updates after the conversion. If delta updates
    are to be performed from different R/3 System clients for this
    DataSource, you first need to initialize the delta method for these
    clients.
    The conversion must be performed separately in each R/3 System because
    the timestamp information is always dependent on the current R/3 System
    and is reset during the transport. If, however, a converted DataSource
    is inadvertently transported into a system in which it has not yet been
    converted, delta extraction will no longer work in the target system
    because the timestamp information is deleted during the import into the
    target system and is not converted to the timestamp information of the
    generic delta. If in this instance no new delta initialization is going
    to be performed in the target system for the DataSource, you can execute
    program ZZUPD_ROOSGENDLM_FROM_TKEBWTS from SAP Note 776151 for the
    DataSource. This program reconstructs the current time stamp information
    from the information for the data packages transported thus far and
    enters this time stamp information into the time stamp information for
    the generic delta. Once this program has been applied, delta extraction
    should work again. Normally, however, you should ensure during the
    transport that the DataSource uses the same logic in the source system
    and the target system.
    After the conversion, the DataSource must be replicated again from the
    SAP BW system.
    A successful conversion is recorded in the notes on the DataSource,
    which you can view in the IMG activity Display Detailed Information on
    DataSource.
    Since the generic delta does not offer any other log functions apart
    from the timestamp information (status: Plug-In Release PI2004.1),
    Profitability Analysis still logs the delta initialization requests or
    delta requests. However, the information logged, in particular the
    timestamps, only has a statistical character because the actual
    timestamp management occurs in the generic delta. Since the delta method  can be performed simultaneously for the same R/3 System client using the
      generic delta from several SAP BW systems, the information logged is
      stored for each logical system (in R/3) and SAP BW system. When a delta
      initialization is simulated, only the timestamp of the generic delta is
      set; Profitability Analysis is not called. Consequently, no information
      can be logged in this case. Messages concerning a DataSource are only
      saved for each logical system (in R/3). You can use the IMG activity
      Display Detailed Information on DataSource to view the information
      logged.
      Another enhancement from Plug-In Release PI2004.1 means that you can no
      longer exclusively perform full updates for DataSources of the Extractor
      Checker of the Service API that have recently been created or converted
      to the generic delta. The following update modes are possible:
      o   F - Full update: Transfer of all requested data
      o   D - Delta: Transfer of the delta since the last request
      o   R - Repeat transfer of a data package
      o   C - Initialization of the delta transfer
      o   S - Simulation of the initialization of the delta transfer
      In the case of all update modes other than F, you have to specify an SAP
      BW system as the target system so that the corresponding timestamp
      and/or selection information for reading the data is found. The Read
      only parameter is set automatically and indicates that no timestamp
      information is changed and that Profitability Analysis does not log the
      request.
      Update mode I (transfer of an opening balance for non-cumulative values)
      is not supported by Profitability Analysis.
    Assign Points if useful
    Regards
    Venkata Devaraj

  • How can I remove a digest-request?

    In Console, I see this appearing every few seconds:
    2015-03-24 3:40:05.161 PM digest-service[2795]: digest-request: user=MYUSERNAME\othername
    2015-03-24 3:40:05.162 PM digest-service[2795]: digest-request: kdc failed with 36150275 proto=unknown
    2015-03-24 3:40:05.162 PM digest-service[2795]: digest-request: guest failed with 22 proto=ntlmv2
    it's remnants of a LabTech install that I removed. I used their uninstaller, but it seems to be still polling every few seconds.
    How can I stop this?

    Hi,
    It is easilly possible to delete the cofile and the datafile of the released transport request but why would you need to do that ?
    It is also possible to delete a transport request in the transport tables but it is a very bad idea and could even be seen as a temptative to hide a forbidden action in the system.
    It will be seen by a security audit as this would create a hole in the request order numbering.
    You would need to use direct database access to delete a released transport request.
    As I told you before, I would NOT do it as it is hasardous et may generate security audit problems.
    You can also destroy your transport system.
    Transport requests are stored in table E070.
    We only modify the e070 table after system copy by database refresh to reset the next transport request number. It is done by inserting a line in the table. We never delete inside this table.
    Use at your own risk !
    Regards,
    Raj.

  • Ringtone selection question

    Hi,
    I don't know if I'm using the correct terminology in English since my phone is set up for Norwegian language, but here's my question:
    When I have been selecting ringtones or notification sounds specific to different apps (email, gmail, text messages), I have been given the choice where I want to browse for ringtones. I am also presented with the choice if I want to browse in a location just one time or always. I have been choosing "Just one time", since I wish to have the choice of location next time. Well, today I accidentally chose "Always", and I can't figure out how to reset / undo that so I can choose from different locations in the future. For instance, I download ringtones/notifications from Zedge, and Zedge has appeared as a choice for where I want to retrieve a ringtone. But now it's not an option anymore. Is there a way to undo / reset this so I can pick from music, system tones, Zedge etc.?

    Settings-apps-all,tap on 3 dots and select reset app preferences.
    All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

  • Is there a way to undo a factory setting reset?

    I recently reset my iphone back to factory settings by accident when updating to the latest ios8 and I lost all of my text message history. Is there a way to undo reset or uncover my text messages?

    If you've ever backed up your device you can restore your phone from that backup....but data will only be from the date of that backup. Let's say you backed up your device in September. Accidentally erased it in November. If you restore it from that backup it'll look like it did in september, but any and all data put on it between september and November will be gone.

  • Inconsistent Results from Transport Rule to reset SCL

    I have a client who has multiple sites. Their exchange server receives "scan to email" emails from a Canon C2020 Digital Multifunction on a different site. To stop the Exchange 2013 Spam filter blocking the emails, I set up a Transport Rule.
    The rule has the following properties
    If the Sender Address matches [email protected]
    Set the SCL to 3
    Generate an incident report and email to the system admin, and inlcude the original email
    Is the 3rd of 3 rules (the prior 2 add Disclaimers to outgoing emails depending on who the sender is)
    Simple enough right.
    Wrong - some staff scan to email repeatedly and the scan arrives ok in their inbox.  Others, it simply will not let the email thru, and instead places the email into the Spam Mailbox.  I open the blocked email, click on Send Again and
    it arrives for the user.
    Is the Transport Rule functionality buggy or prone to odd behaviour.  I have sat and read through the Rule so many times it is tattooed onto my retina.
    The Email addresses for all users are created by an Email address policy so all are a consistent format = Firstname + Surname 1st Initial@contoso .com.
    There have been times where I have wondered if the rules are case sensitive when assessing the email addresses.
    Any thoughts to put me out of my misery, please show me where I have done wrong....
    Get-TransportRule returns
    [PS] C:\Windows\system32>Get-TransportRule "[Cust-sos-IN] Reset SCL on Scanner emails" | Format-List
    RunspaceId                                   : 7f9c4f6e-7d35-409e-acf9-cbb272720b8c
    Priority                                     : 2
    DlpPolicy                                    :
    DlpPolicyId                                  : 00000000-0000-0000-0000-000000000000
    Comments                                     :
    ManuallyModified                             : False
    ActivationDate                               :
    ExpiryDate                                   :
    Description                                  : If the message:
    Is sent to '[email protected]' or
    '[email protected]' or
    '[email protected]' or
    '[email protected]' or
    '[email protected]' or
    '[email protected]' or
    '[email protected]'or...
    and Includes these patterns in the From address:
    '[email protected]'
    Take the following actions:
    Set the spam confidence level (SCL) to '3'
    and Send the incident report to [email protected], Include
    original mail
    RuleVersion                                  : 15.0.2.0
    Conditions                                   : {SentTo, FromAddressMatches}
    Exceptions                                   :
    Actions                                      : {SetSCL, GenerateIncidentReport}
    State                                        : Enabled
    Mode                                         : Enforce
    RuleSubType                                  : None
    UseLegacyRegex                               : False
    From                                         :
    FromMemberOf                                 :
    FromScope                                    :
    SentTo                                       :
    {[email protected],
    [email protected],
    [email protected],
    [email protected],
    [email protected],
    [email protected],
    [email protected],
    [email protected], [email protected],
    [email protected],
    [email protected], [email protected],
    [email protected],
    [email protected], [email protected],
    [email protected]...}
    SentToMemberOf                               :
    SentToScope                                  :
    BetweenMemberOf1                             :
    BetweenMemberOf2                             :
    ManagerAddresses                             :
    ManagerForEvaluatedUser                      :
    SenderManagementRelationship                 :
    ADComparisonAttribute                        :
    ADComparisonOperator                         :
    SenderADAttributeContainsWords               :
    SenderADAttributeMatchesPatterns             :
    RecipientADAttributeContainsWords            :
    RecipientADAttributeMatchesPatterns          :
    AnyOfToHeader                                :
    AnyOfToHeaderMemberOf                        :
    AnyOfCcHeader                                :
    AnyOfCcHeaderMemberOf                        :
    AnyOfToCcHeader                              :
    AnyOfToCcHeaderMemberOf                      :
    HasClassification                            :
    HasNoClassification                          : False
    SubjectContainsWords                         :
    SubjectOrBodyContainsWords                   :
    HeaderContainsMessageHeader                  :
    HeaderContainsWords                          :
    FromAddressContainsWords                     :
    SubjectMatchesPatterns                       :
    SubjectOrBodyMatchesPatterns                 :
    HeaderMatchesMessageHeader                   :
    HeaderMatchesPatterns                        :
    FromAddressMatchesPatterns                   :
    {[email protected]}
    AttachmentNameMatchesPatterns                :
    AttachmentExtensionMatchesWords              :
    HasSenderOverride                            : False
    MessageContainsDataClassifications           :
    SenderIpRanges                               :
    SCLOver                                      :
    AttachmentSizeOver                           :
    MessageSizeOver                              :
    WithImportance                               :
    MessageTypeMatches                           :
    RecipientAddressContainsWords                :
    RecipientAddressMatchesPatterns              :
    SenderInRecipientList                        :
    RecipientInSenderList                        :
    AttachmentContainsWords                      :
    AttachmentMatchesPatterns                    :
    AttachmentIsUnsupported                      : False
    AttachmentProcessingLimitExceeded            : False
    AttachmentHasExecutableContent               : False
    AnyOfRecipientAddressContainsWords           :
    AnyOfRecipientAddressMatchesPatterns         :
    ExceptIfFrom                                 :
    ExceptIfFromMemberOf                         :
    ExceptIfFromScope                            :
    ExceptIfSentTo                               :
    ExceptIfSentToMemberOf                       :
    ExceptIfSentToScope                          :
    ExceptIfBetweenMemberOf1                     :
    ExceptIfBetweenMemberOf2                     :
    ExceptIfManagerAddresses                     :
    ExceptIfManagerForEvaluatedUser              :
    ExceptIfSenderManagementRelationship         :
    ExceptIfADComparisonAttribute                :
    ExceptIfADComparisonOperator                 :
    ExceptIfSenderADAttributeContainsWords       :
    ExceptIfSenderADAttributeMatchesPatterns     :
    ExceptIfRecipientADAttributeContainsWords    :
    ExceptIfRecipientADAttributeMatchesPatterns  :
    ExceptIfAnyOfToHeader                        :
    ExceptIfAnyOfToHeaderMemberOf                :
    ExceptIfAnyOfCcHeader                        :
    ExceptIfAnyOfCcHeaderMemberOf                :
    ExceptIfAnyOfToCcHeader                      :
    ExceptIfAnyOfToCcHeaderMemberOf              :
    ExceptIfHasClassification                    :
    ExceptIfHasNoClassification                  : False
    ExceptIfSubjectContainsWords                 :
    ExceptIfSubjectOrBodyContainsWords           :
    ExceptIfHeaderContainsMessageHeader          :
    ExceptIfHeaderContainsWords                  :
    ExceptIfFromAddressContainsWords             :
    ExceptIfSubjectMatchesPatterns               :
    ExceptIfSubjectOrBodyMatchesPatterns         :
    ExceptIfHeaderMatchesMessageHeader           :
    ExceptIfHeaderMatchesPatterns                :
    ExceptIfFromAddressMatchesPatterns           :
    ExceptIfAttachmentNameMatchesPatterns        :
    ExceptIfAttachmentExtensionMatchesWords      :
    ExceptIfSCLOver                              :
    ExceptIfAttachmentSizeOver                   :
    ExceptIfMessageSizeOver                      :
    ExceptIfWithImportance                       :
    ExceptIfMessageTypeMatches                   :
    ExceptIfRecipientAddressContainsWords        :
    ExceptIfRecipientAddressMatchesPatterns      :
    ExceptIfSenderInRecipientList                :
    ExceptIfRecipientInSenderList                :
    ExceptIfAttachmentContainsWords              :
    ExceptIfAttachmentMatchesPatterns            :
    ExceptIfAttachmentIsUnsupported              : False
    ExceptIfAttachmentProcessingLimitExceeded    : False
    ExceptIfAttachmentHasExecutableContent       : False
    ExceptIfAnyOfRecipientAddressContainsWords   :
    ExceptIfAnyOfRecipientAddressMatchesPatterns :
    ExceptIfHasSenderOverride                    : False
    ExceptIfMessageContainsDataClassifications   :
    ExceptIfSenderIpRanges                       :
    PrependSubject                               :
    SetAuditSeverity                             :
    ApplyClassification                          :
    ApplyHtmlDisclaimerLocation                  :
    ApplyHtmlDisclaimerText                      :
    ApplyHtmlDisclaimerFallbackAction            :
    ApplyRightsProtectionTemplate                :
    SetSCL                                       : 3
    SetHeaderName                                :
    SetHeaderValue                               :
    RemoveHeader                                 :
    AddToRecipients                              :
    CopyTo                                       :
    BlindCopyTo                                  :
    AddManagerAsRecipientType                    :
    ModerateMessageByUser                        :
    ModerateMessageByManager                     : False
    RedirectMessageTo                            :
    RejectMessageEnhancedStatusCode              :
    RejectMessageReasonText                      :
    DeleteMessage                                : False
    Disconnect                                   : False
    Quarantine                                   : False
    SmtpRejectMessageRejectText                  :
    SmtpRejectMessageRejectStatusCode            :
    LogEventText                                 :
    StopRuleProcessing                           : False
    SenderNotificationType                       :
    GenerateIncidentReport                       :
    [email protected]
    IncidentReportOriginalMail                   : IncludeOriginalMail
    RouteMessageOutboundConnector                :
    RouteMessageOutboundRequireTls               : False
    Identity                                     : [Cust-sos-IN] Reset SCL on Scanner
    emails
    DistinguishedName                            : CN=[Cust-sos-IN] Reset SCL on Scanner
    emails,CN=TransportVersioned,CN=Rules,CN=Transport
    Settings,CN=Contoso,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=CONTOSO,DC=LOCAL
    Guid                                         : 5d1dbc9b-3718-4874-9552-296e8b98d874
    ImmutableId                                  : 5d1dbc9b-3718-4874-9552-296e8b98d874
    OrganizationId                               :
    Name                                         : [Cust-sos-IN]
    Reset SCL on Scanner emails
    IsValid                                      : True
    WhenChanged                                  : 17/03/2015 2:37:06 PM
    ExchangeVersion                              : 0.1 (8.0.535.0)
    ObjectState                                  : Unchanged

    Hi MBKITMGR,
    Agree with Zammit, you should use the BypassedSenders parameter to specifies the SMTP address values of senders.
    After that, the Content Filter agent doesn't process any content filtering for messages received from the addresses listed on this parameter.
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

Maybe you are looking for