Scribd Logo
Upload

Welcome to Scribd!

  • 320 views

    SAP MM Release Strategy Deletion

    Uploaded by

    dinugypsy123-1
    The document discusses an issue where a purchase requisition was assigned an incorrect release code not related to its assigned release strategy. An investigation found the release strategy had been deleted directly from a table without following the proper sequence, creating an inconsistency. The permanent solution is to delete release strategies and related objects in the proper sequence and check tables to ensure all data is cleared without inconsistencies.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    SAP MM Release Strategy Deletion

    Uploaded by

    dinugypsy123-1
    320 views3 pages
    The document discusses an issue where a purchase requisition was assigned an incorrect release code not related to its assigned release strategy. An investigation found the release strategy had been deleted directly from a table without following the proper sequence, creating an inconsistency. The permanent solution is to delete release strategies and related objects in the proper sequence and check tables to ensure all data is cleared without inconsistencies.

    Original Description:

    SAP MM Release Strategy Deletion

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses an issue where a purchase requisition was assigned an incorrect release code not related to its assigned release strategy. An investigation found the release strategy had been deleted directly from a table without following the proper sequence, creating an inconsistency. The permanent solution is to delete release strategies and related objects in the proper sequence and check tables to ensure all data is cleared without inconsistencies.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    320 views3 pages

    SAP MM Release Strategy Deletion

    Uploaded by

    dinugypsy123-1
    The document discusses an issue where a purchase requisition was assigned an incorrect release code not related to its assigned release strategy. An investigation found the release strategy had been deleted directly from a table without following the proper sequence, creating an inconsistency. The permanent solution is to delete release strategies and related objects in the proper sequence and check tables to ensure all data is cleared without inconsistencies.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    You are on page 1of 3

    SAP MM Release Strategy Deletion

    07/03/2008

    INDIA\SAP\MANUFACTURING
    S.SASIKUMAR
    s.sasikumar@tcs.com

    SAP MM Release strategy deletion

    Problem
    When a Purchase Requisition (PR) using t-code ME51 is created and saved,
    a release strategy to the PR is assigned..
    When the release strategy assigned to the PR for releasing is checked, a
    wrong release code in the release-to-date is found, which is not related to
    the release strategy.

    Observation and Analysis


    The configuration of the release strategy 24 had been checked and the
    wrong release code (15) had not been found.
    The table - T16FS - Release Strategies had been checked and there were
    no wrong release codes found.
    But in table - T16FV - Release Pre-requisites, the wrong release code (15)
    was found and the release strategy was deleted directly without following
    the sequence; hence an inconsistency has been created in table T16FV.
    It was deleted as the release strategy earlier was customized at
    Header level and later was changed to Item level. When it was
    directly corrected in customizing, it did not update the tables
    properly. Hence in tables T16FK, T16FV, T16FS, T16FC and T16FG,
    there will be entries from previous customizing settings (for example, old
    release groups) that were indeed deleted from the customizing settings,
    but not deleted from the tables. This creates an inconsistency.

    Solution:
    Temporary solution:
    1. The correct solution may be deleting these release strategies and
    transporting to the production client, checking all tables for clearing the
    data, recreating and then transporting to the production system. This is a
    long but perfect method.
    2. If there are very few inconsistencies and we have clearly identified
    these, table level correction can be done. This is a short but not a much
    recommended method. This should be done strictly in SAP's control.

    Tata Consultancy services

    Internal use

    Page 2 of

    SAP MM Release strategy deletion

    Permanent solution:
    To avoid inconsistency during Release strategy deletion, SAP has
    recommended a procedure to follow:
    1. Delete the release strategies
    2. Delete the release indicators
    3. Delete the release codes
    4. Delete the release group
    5. Delete the class (Transaction CL02), provided a new one has been
    created for the new release strategies.
    Further use Transaction SE16 to check if the entries in the tables
    mentioned above were deleted. Execute the report in Customizing
    (Transaction OMGQCK or OMGSCK) and ensure that the system does not
    display any red traffic lights.

    Tata Consultancy services

    Internal use

    Page 3 of

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy