Explanation of the InfoSources tree:

The application components are arranged under the root:
@6F@ Application component.

The InfoSources and InfoObjects for which data can be loaded from thesource systems in question are ordered under an application component:
@6E@ InfoSource for transaction data.
@81@ Active characteristic (InfoObject) for which master data, texts andhierarchies can be collected.
@82@ Inactive characteristic (InfoObject) for which master data, textsand hierarchies can be collected, as soon as it is activated.

Those source systems that can deliver data for this InfoSource /InfoObject are arranged under an InfoSource / InfoObject:
@6K@ SAP source system.
@6L@ BAPI source system.
@6M@ External system (PC file on the workstation or file on theapplication server).
The InfoPackages that contain the selections with which you request thedata and with which you control when the data should be collected (andwhich InfoCubes should be updated with the transaction data) arearranged under the source systems:
@9N@ InfoPackage.

Meaning of the buttons in the columns after the node name:

On the application component level:
There are no buttons.

On the InfoSources and InfoObjects (characteristics) level:
@6V@ InfoObject with active communication structure for loading masterdata.
@6W@ InfoObject without active communication structure for loadingmaster, or inactive InfoObject.
@6X@ Active InfoObject with the possibility of loading texts.
@6Y@ InfoObject is inactive, for which texts can be loaded afteractivation.
@6Z@ Active InfoObject with the possibility of loading hierarchies.
@70@ Inactive InfoObject with the possibility of loading hierarchiesafter activation.
@71@ InfoSource with active communication structure for loadingtransaction data.
@72@ InfoSource without active communication structure for loadingtransaction data.

On the source systems level:
@6V@ An active transfer rule for loading master data exists between thissource system and the superior InfoObject.
@6W@ No active transfer rule for loading master data exists between thissource system and the superior InfoObject.
@6X@ The possibility exists, of loading texts for the superiorInfoObject from this source system.
@6Z@ The possibility exists, of loading hierarchies the superiorInfoObject from this source system.
@71@ An active transfer rule exists for loading transaction data betweenthis source system and the superior InfoObject.
@72@ No active transfer rule exists for loading transaction data betweenthis source system and the superior InfoObject.

On the InfoPackages level:
@6V@ This InfoPackage can be used for loading master data for thesuperior InfoObject from the relevant source system.
@6X@ This InfoPackage can be used for loading texts for the superiorInfoObject from the relevant source system.
@6Z@ This InfoPackage can be used for loading hierarchies for thesuperior InfoObject from the relevant source system.
@71@ This InfoPackage can be used for loading transaction data for thesuperior InfoObject from the relevant source system.
@1T@ This InfoPackage is scheduled in the SAP background processing.Data should be collected at a later point in time.

General:
@5Y@ This object was delivered by SAP.