Functional Prerequisites for Message Determination (SAP Library

Functional Prerequisites for Message Determination

In Subsequent Settlement, messages relating to rebate arrangements and settlement runs for arrangements are issued using message determination, and this process is controlled via the arrangement type. The following settings must be maintained for this in Customizing for the arrangement type:

Message schema for the rebate arrangement
Message type for the rebate arrangement
Message schema for the settlement run
Message type for the settlement run

The condition technique uses the following applications for Subsequent Settlement:

Message application WS for messages for rebate arrangement
Message application WN for messages for settlement runs

Message determination uses the condition technique. Below is a brief overview of the elements and settings that are required in Customizing for Subsequent Settlement.

Condition tables

A condition table defines the combination of fields for which message records are created. Standard condition table 160 controls message determination dependent on the combination of purchasing organization and condition granter, for example.

In addition to the standard condition tables, you can define your own condition tables.

Message types

The message type in the SAP system is used to map different messages such as the output of credit-side or debit-side rebate arrangements, and settlement runs. In addition, the message type defines which transmission medium is used, and when and to which business partner the message is sent.

In addition to the standard message types (such as WSDK for credit-side rebate arrangements and WNAK for settlement runs for credit-side rebate arrangements), you can create your own message types.

Note

Condition records must exist for the message types, so that default values are available for the transmission medium, business partner, transmission time and so on. For further information, see Creating Condition Records.

Access sequences

Access sequences are search strategies that the SAP system uses to find valid condition records.

In addition to the standard access sequences, you can define your own access sequences.

Message schemas

The message schemas contain the permitted message types. This enables a default value to be generated for the messages. In addition to the standard message schemas, you can define your own message schemas.

In addition to these elements of the condition technique, the following settings must be maintained for message determination:

Message types must be assigned to the partner functions.

The permitted type of message processing (such as printing or faxing) must be entered for a particular combination of message type and partner function.

SAPscript forms (for printing and faxing) and programs must be assigned to the individual message types.

The forms control the layout of the output documents, and the programs control message processing.

In the standard system, a program and a form enabling print output are already assigned to each message type.

Note

You can choose Define forms to change existing forms and create new ones.

You can choose Assign form texts to define which texts for address, letter header, footer, and style of greeting appear in the output document, dependent on purchasing organization and sales organization.

You can define print parameters dependent on the following keys:

Sales organization/distribution channel/division
Sales organization
Purchasing group

For information on the individual Customizing settings, see the implementation guide (IMG).