!--a11y-->
Example: CSA Table 
Suppose you specify the parameters for Customer Service Area (CSA) table as follows:
Table Name |
Field Name |
Sequence |
Key |
VBAK |
KUNNR (customer number) |
3 |
|
KUAGV |
BLAND (location) |
2 |
X |
VBAP |
WERKS (plant) |
1 |
X |
KUWEV |
ORT01 (ship-to location) |
4 |
|
Only those fields designated as key fields are stored in the CSA table.
Whenever sales orders are created, the system looks at the key fields Location and Plant to see if they form a unique combination. In this case, the key fields are the customer location in the header data and the plant in the schedule line data.
Now suppose that you have five incoming orders (A, B, C, D, and E). The system processes the orders as follows:
Sales order A is for location NY and plant Buffalo. Since you just created the CSA table, it is empty and therefore this combination of NY and plant Buffalo is unique. The system writes a line in the CSA table for this combination, and this becomes Customer Service Area 1...
1. Sales order A is for location NY and plant Buffalo. Since you just created the CSA table, it is empty and therefore this combination of NY and plant Buffalo is unique. The system writes a line in the CSA table for this combination, and this becomes Customer Service Area 1.
2. Sales order B is for location CA and plant Los Angeles. The system compares this combination of key fields against the existing line in the CSA table. Since this new combination is unique, the system again writes a line in the CSA table. This becomes Customer Service Area 2.
3. Sales order C is again for location NY and plant Buffalo. The system compares these key fields against entries in the CSA table: this combination already exists in the CSA table, so it does not update the CSA table.
4. Sales order D is for location NY and plant Newark. (Although the sales order is from a New York customer, the closest plant is in New Jersey so that is where the delivery originates.) Although the key field entry NY already exists in the table, the combination of NY and Newark does not. So the system writes another line in the table. This becomes Customer Service Area 3.
5. Sales order E is for location AZ and plant Los Angeles. Although Los Angeles already exists in the table, location AZ does not. The system writes another line in the table for Customer Service Area 4.
After the system processes these five sales orders, the previously empty CSA table now contains four lines corresponding to four sales areas. (Key fields are shaded in gray.)
Plant |
Location |
Customer Number |
Ship-To Location |
CSA Number |
Buffalo |
NY |
10000 |
Syracuse |
0000000001 |
Los Angeles |
CA |
10023 |
San Diego |
0000000002 |
Newark |
NY |
11894 |
Brooklyn |
0000000003 |
Los Angeles |
AZ |
12445 |
Phoenix |
0000000004 |