Kontakt

Ansicht
Dokumentation

W_WLFA_E003 - Maintain Access Sequences

W_WLFA_E003 - Maintain Access Sequences

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define the access sequences for use in Settlement Management.

The access sequence is a search strategy that the SAP system uses to find valid message records.

To define an access sequence, you must make the following entries:

  1. Access sequence
Alphanumeric key with up to 4 characters, which uniquely identifies the access sequence.
  1. Description
Text that describes the access sequence.
  1. Detailed data (only the most important detailed data is explained here, for further information, see the field help):
    1. Sequence number
      Sequence number of the access in the access sequence.
    2. Table
      Condition table that contains the key fields of the message records.

The following entries are provided in the standard SAP system:

  • WRK1: Header messages (output), supplier-side, with logistics data:
  • The system first accesses condition table 170 (purchasing organization and invoicing party).

  • If this is unsuccessful, it accesses condition table 172 (company code and invoicing party).

  • WRK2: Header messages (output), supplier-side, without logistics data:
  • The system accesses condition table 172 (company code and invoicing party).

  • WRK3: Header messages (output), customer-side, with logistics data:
  • The system first accesses condition table 171 (sales org./distribution channel/division and payer).

  • If this is unsuccessful, it accesses condition table 173 (company code and payer).

  • WRK4: Header messages (output), customer-side, without logistics data:
  • The system accesses condition table 173 (company code and payer).

  • WRK5: Header messages (output) with logistics data:
  • The system first accesses condition table 170 (purchasing organization and invoicing party).

  • If this is unsuccessful, it accesses condition table 171 (sales org./distribution channel/division and payer).

  • If this is unsuccessful, it accesses condition table 172 (company code and invoicing party).

  • If this is unsuccessful, it accesses condition table 173 (company code and payer).

  • WRK6: Header messages (output) without logistics data
  • The system first accesses condition table 172 (company code and invoicing party).

  • If this is unsuccessful, it accesses condition table 173 (company code and payer).

  • WRP1: Item message (output), supplier-side, with logistics data:
  • The system first accesses condition table 170 (purchasing organization and invoicing party).

  • If this is unsuccessful, it accesses condition table 172 (company code and invoicing party).

  • WRP2: Item messages (output), supplier-side, without logistics data:
  • The system accesses condition table 172 (company code and invoicing party).

  • WRP3: Item messages (output), with logistics data:
  • The system first accesses condition table 170 (purchasing organization and invoicing party).

  • If this is unsuccessful, it accesses condition table 171 (sales org./distribution channel/division and payer).

  • If this is unsuccessful, it accesses condition table 172 (company code and invoicing party).

  • If this is unsuccessful, it accesses condition table 173 (company code and payer).

  • WRP4: Item message (output) without logistics data:
  • The system first accesses condition table 172 (company code and invoicing party).

  • If this is unsuccessful, it accesses condition table 173 (company code and payer).

  • WRP5: Item messages (output), customer-side, with logistics data:
  • The system first accesses condition table 171 (sales org./distribution channel/division and payer).

  • If this is unsuccessful, it accesses condition table 173 (company code and payer).

  • WRP6: Item messages (output), customer-side, without logistics data:
  • The system accesses condition table 173 (company code and payer).

To create an access sequence, copy a similar, existing access sequence and make the necessary changes.

If you define your own access sequences, take account of the name space conventions.

  1. Check the extent to which you can use the standard SAP access sequences and how much you would have to change these.
  2. Define your access sequences for use in Settlement Management.






PERFORM Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 6412 Date: 20240523 Time: 173208     sap01-206 ( 42 ms )