Ansicht
Dokumentation

REB_CTCT - Create Condition Tables

Addresses (Business Address Services)   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

In this activity, you create condition tables for different usages, for example, rebates, pricing, campaign determination, product substitution or free goods determination.

You use a condition table to determine the combination of fields for which a condition record should consist. The number of fields used for a condition table is restricted to 10.

The condition table consists of a combination of search and results fields:

• The system can search for condition records later using the search fields. You can freely define the search fields.

• The results fields contain the values that the system provides for the business transaction that triggered the search for the condition record. The results fields are predefined by the selected usage, and are not displayed when creating a condition table.

Before creating a new condition table, check whether existing fields are sufficient for your requirements. If you require a field that is not provided in the condition tables of the standard delivery, you have to include it in the field catalog. Fields that can be copied to condition tables, can only have a certain data type:

The following fields are permitted for fields used as a search criterion when searching for a condition record:

• ACCP Posting period JJJJMM

• CHAR Character string

• CUKY Currency key, referenced from CURR fields

• DATS Date field (JJJJMMDD), stored as Char(8)

• LANG Language key

• NUMC Character string with numbers only

• RAW Uninterpreted sequence of bytes

• TIMS Time field (hhmmss), stored as Char(6)

• UNIT Unit key for QUAN fields

The following fields are permitted as results fields when you have searched for a condition record:

• CURR Currency field, stored as DEC

• DEC Calculation or amount field with comma and plus/minus sign

• FLTP Floating point number with 8 byte precision

• INT1 1-byte integer <= 255

• INT2 2-byte integer, only for length field before LCHR or LRAW

• INT4 4-byte integer with plus/minus sign

• PREC precision of a QUAN field

• QUAN Quantity field shows on a sunit field with UNIT format

You cannot, under any circumstances, include any of the following data types in condition table fields:

• CLNT Client

• LCHR Long character string; requires preceding INT2 field

• LRAW Long byte string; requires preceding INT2 field

• RSTR Variable length string of bytes

• SSTR Short variable length character string

• STRG Variable length character string

• VARC Long character string; no longer supported as of Release 3.0

1. Check to what extent you can use the condition tables delivered with the standard configuration.
2. Proceed as follows to create new condition records:
1. Enter the name of the table that you would like to create. The name must begin with CUS in a customer system. After that you can enter a maximum 5-digit number.
2. Enter a description for the condition table. If you do not enter a description, the system will generate one using the field names in the table when you save.
3. Choose the required fields for the condition table from the list of permitted fields contained in the field catalog.
4. You can also include fields as non-search fields. In this case, the search does not take place with this field, rather the content of the field can be determined by formulae or conditions for the inquiry.
5. Save the new condition table. The system automatically includes the table in a transprot request. An individual object with the following name construction is generated for the transport:

Object type: CTCT

Object name: Z (customer-specific), or A (SAP) + table number/application/usage

Example of object name:

Application: CRM

Usage: PR

Table number: SAP004

Object name: ASAP004_CRMPR

The number of alphanumeric characters provided for application, usage and table number in the object name is constant. This number of characters equals 3 for application, 2 for usage and 2 for table number. If the actual number for the application, usage or table number is less than the constant within the object name, then the difference is filled with '_'.

1. Activate the condition table; the transport request is only released once this has taken place.
2. Enter the condition tables in the access sequences; this is how you create the connection between the condition type, access sequence and condition record.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Material Data  
This documentation is copyright by SAP AG.

Length: 5723 Date: 20240523 Time: 190937     sap01-206 ( 72 ms )