Defining Access Sequences 

  1. To define an access sequence, you can choose one of the two following alternatives:
    2.

    · Select the appropriate activity from Customizing in the relevant application

    · Use transaction NACE in expert mode. The following describes this alternative.

  2. Select your application and select Edit ® Access sequences.
  3. In change mode you define new access sequences or change existing ones. This also involves the allocation of application fields to the key fields of the relevant condition table.

    4. The key is defined in message determination from the current values of the assigned application fields. The condition table is then read with this key. This is table access.

  4. You can use an ABAP condition for access for each condition table. You define new conditions with transaction V/27.

    5. If the condition is met, then the system does not access the condition table. You can also define conditions in Procedures.

  5. You can set the "exclusive" indicator for each condition table.

    6. If access to a table indicated as exclusive was successful, then the system does not search any further for messages in the access sequence. Instead it continues with the next output type defined in the procedure.

  6. Save your entries.

The following illustration shows access sequences for sales documents. Subsequent explanations will concern access sequence 0003 of this list.

 

The following illustration shows access sequence 0003 being used to access condition table 001. Here you define the accesses and their order in the access sequence.

The following illustration shows which fields are used to access the condition table. The sold-to party is transferred as the customer number (in contrast for example to the ship-to party). This partner function "sold-to party" is defined as the standard default value for the condition records of the output type order confirmation (BA00).