Skip to Content
author's profile photo Former Member
Former Member


What is the importance of release status and dynamic field check in condition table/condition record

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Aug 30, 2007 at 04:07 AM


    <b>Dynamic Field Check</b>

    When maintaining condition records in Release 4.6A, you can check all of the fields for valid values. If there is a text table for the individual values, these texts can be determined for the individual values. Some fields in the system are purposely not checked however, because it is not necessary (for example, the fields product hierarchy and document number are not checked in the system)

    The check can be done using value tables or fixed values in the SAP dictionary. The special check available before, for example, from the customer or product remains unchanged.

    This is a dynamic field check because customer specific fields are automatically included in the check. For checking customer-specific fields the fields must be available in the communication structure KOMG and the value tables or fixed values must be maintained in the SAP dictionary. A foreign key check is also possible.

    If you want to switch off the check for individual fields or want to configure these fields yourself, the following Business Transaction Events (BTE) are available (transaction FIBF):

    • 00503305 Maintaining conditions: Field check

    • 00503306 Maintaining conditions: Text determination

    <b>Release Procedures</b>

    You can use a release procedure, which allows you, for example, to create condition records purely for planning purposes, which are then only taken into consideration after a pricing release. For this release procedure, you can use the processing and release statuses. You are free to define and use a processing status, although the release status can not be maintained by you directly but results indirectly from your assignment to a processing status.

    NoteThe release status and processing status are only available for the new condition tables (see standard system section). If you also want to use this status for condition records that already exist, you can convert this (see Conversion section).

    <b>Release Status</b>

    The release status is already set. You can only set a processing status using assignment and selection of a processing status. The following statuses are currently defined:

    • released

    • blocked

    • released for price simulation (this means the creation of a net price list using the report SDNETPR0)

    • released for planning (this means planning in CO-PA) and price simulation

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.