Unit 1: ALE Fundamentals BIT300
convention <System name>CLNT<Client key>. In the example illustrated below,
the SAP system has the key G23. Clients 800, 810 and 811 are used. Thus, for
example, client 800 receives the logical system name G23CLNT800.
Note: The terms “logical sys t em name” and “logical system” are used
interchangeably.
Figure 7: Logical System Names
In certain cases, it could be useful not to use SAP's recommended convention
for logical system names. The training clients for this course have “descriptive”
names: the logical system name for head office is CORE, sales and distribution is
called SALES andproductionisPRODUCTION. Naming the systems in this
way is an alternative to the SAP convention if the assignment of clients to logical
system names is frequently changed.
Caution: Changing the logical system name is a s erious intervention, as
this name is included in numerous application tables (see lesson on “Basic
ALE Customizing” and appendix “Renaming Logical Systems”).
Message Type
When configuring an ALE scenario, in addition to assigning logical system
names, you also need to indicate the types of data that are to be exchanged: if,
for example, you want to distribute material masters with ALE in the future, you
need to name the type of data (material masters) with what is known as a message
type (MATMAS). Mes sage types are therefore essentially keys, comparable to
logical system names, which indicate data that can be exchanged between systems
in ALE or EDI scenarios.
10 © 2006 SAP AG. All rights reserved. 2005/Q4
我的内容管理
展开
