SAP ABAP IMG Activity W_WLFA_E003 (Maintain Access Sequences)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ LO-AB (Application Component) Agency Business (Global Trade)
     ⤷ WZRE (Package) Agency Business
IMG Activity
ID W_WLFA_E003 Maintain Access Sequences  
Transaction Code S_ALR_87100030   (empty) 
Created on 19990409    
Customizing Attributes W_WLFA_E003   Maintain Access Sequences 
Customizing Activity W_WLFA_E003   Maintain Access Sequences 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name W_WLFA_E003    

In this step, you define the access sequences for Agency Business.

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.

  2. Description

    Text that describes the access sequence.

  3. 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.

Example

Requirements

Standard settings

The following entries are provided in the standard SAP system:

  • WRK1: Header messages (output), vendor-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), vendor-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), vendor-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), vendor-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).

Recommendation

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.

Activities

  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 Agency Business.

Further notes

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG W_WLFA_E003 0 ALR0000097 Agency Business (Global Trade) 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VVC_T682_WR C - View cluster SM34 Maintain Access Sequences for Agency Business 
History
Last changed by/on SAP  19990414 
SAP Release Created in