Hi Vaishali,
they seem to be related to business transfer beetween connected systems. You'll find some documentation in the corresponding datatypes.
<b>REFOBJTYPE</b>
Short Text
Object Type
Definition
Internal technical key of a business object in the Business Object Repository (BOR).
Business objects are identified in the BOR by object type (for example BUS2032) and a descriptive English name (for example SalesOrder). Both identifiers must be unique across all object types.
Business objects are often addressed using the descriptive name from external applications, while internally in the BOR they are mostly identified using the object type. Initially, only the internal key was used, but the extensive use of business objects has given rise to the need for addressing them using names. For compatibility reasons, both identifiers are now used.
The object type can have a maximum of 10 characters.
Examples:
BUS2032
BUS6026
<b>REFOBJKEY</b>
Short Text
Object key
Definition
Linked key for an object.
The key is formed by linking all of the key fields together without any gaps. The key fields are defined for objects of this type in the Business Object Repository.
<b>LOGSYS</b>
Short Text
Logical system
Definition
System in which applications run integrated on a shared data basis.
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).
The logical system is relevant in the following SAP areas:
ALE general: two or more logical systems communicate with one another.
ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.
Workflow objects: the logical system in which the object is located is always included in an object's key.
When maintaining the logical system, note the following:
The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
Hope that helps,
ok
Bluesky
