Customer Local Exceptions

Customer information such as contact information, financial information, insurance details, and delivery terms can be maintained as customer local exceptions in 'Customer. Open Local Exceptions' (MFS610). In (MFS610), customer master data are maintained per division. The program is accessed from 'Customer. Open' (CRS610) through related option 17='Local exception'.

Outcome

The customer local exception data is completed in the customer local exception table with, for example, contact information, financial information, insurance details, and delivery terms.

The table CCUDIV (Customer local exceptions) is updated.

Before you start

A customer must be created.

For more details, see Complete Customer Data.

Follow these steps

  1. Start 'Customer. Open' (CRS610).
  2. Select a customer and use related option 17= 'Local exception' to open 'Customer. Open Local Exceptions' (MFS610).
  3. Select option 1='Create', specify the relevant customer local exception data, and click Next.

Field settings for customer local exceptions

The settings for the fields in (MFS610) are defined per division in 'Settings - Customer Local Exceptions' (CMS702). The settings in (CMS702) control if a customer master field is to be maintained through the customer local exception (MFS610) or the customer master (CRS610). These are the valid field settings:
  • 0-'Not displayed'
  • 1-'Display not change'
  • 2-'Display & change'

The field setting 0-'Not displayed' or 1-'Display not change' implies that the field is not to be maintained through the local exception for the given division. An update in (CRS610) is to be reflected in (MFS610) once (CRS610) is closed.

The field setting 2-'Display & change' implies that the field is to be maintained through a customer local exception. When this setting is selected, the field is never to be automatically synced with the value specified in the customer master (CRS610).

Related topics