Show TOC
Define
Requirements
Requirements are represented by FORM routines.
For example, they are used for the condition technique and for statistics.
Requirements check various criteria during the execution of the respective
functions. You can enter them in the functions of the condition technique in
the pricing procedure.
Example
- In pricing, a requirement checks whether a
condition type is taken into account in the document. The requirement can
define, for example, that a condition type is only taken into account for
import and export transactions.
- Requirement 004 in output control defines that
an output is proposed in the billing document, if the billing document is
complete and not relevant for invoice lists.
- A requirement in account determination can
define, for example, that the account determination is only carried out with
CO objects.
You have to enter the requirements delivered
with the standard system and your own requirements you want to use in the
condition technique functions in the pricing procedure. There, a list of the
requirements available for each function is displayed.
This section describes how to define
requirements according to the specific needs of your organization. The
following communication tables are available to you for the creation of
requirements:
- Pricing (KOMK, KOMP,
T001, T001R)
- Output control (depending on
the application, KOMKBV1, KOMKBV2 or
KOMKBV3 are available)
- Account determination (KOMKCV,
KOMPCV)
- Material determination (KOMKD,
KOMPD)
- Listing/Exclusion (KOMKG,
KOMPG)
Note
A pre-step was included for pricing
requirements as a tuning measure which checks first the KOMK fields. If the
result of the check is negative, the item fields of KOMP do not have to be
checked.
Procedure
1. First check
whether you can use the requirements delivered with the standard
system.
2. Either
overwrite an existing requirement or select a group number from the number
range reserved for customer modifications (600-699) and enter the
corresponding description.
3. Program the
requirement in the editor.
4. Activate the
requirement.
5. Enter a long
text that describes the meaning of the routine in more detail.
6. Enter the
application if you want to use the requirement in one particular application
area only (pricing, for example).
7. Enter the
requirement in the pricing procedure for the function for which you want to
use the requirement.