Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-LIS (Application Component) Logistics Information System (LIS)⤷
MC0C (Package) Customizing Logistics Information System
IMG Activity
| ID | OLIS_ALE | Generate message type |
| Transaction Code | S_ALR_87000809 | IMG Activity: OLIS_ALE |
| Created on | 19981222 | |
| Customizing Attributes | OLIS_ALE | Generate message type |
| Customizing Activity | OLIS_ALE | Generate message type |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OLIS_ALE |
In this step, you configure information structures for use in Application Link Enabling (ALE).
ALE is the technique by which data is exchanged between a central application and distributed applications running on different logical computer systems, sometimes in different countries, in a communications network.
Communication between applications is carried out via the medium of the IDOC (intermediate document). The configuration of all information structures is based on one central reference IDOC. An IDOC used for SOP has ten segments for key figures, one segment for characteristic values, and one segment for the planning version.
You maintain a distribution model for the IDOC of each information structure, in which you define the reference as the sender and the client as the receiver. You can then set up this distribution model such that organizational units (characteristic values) receive only data (key figures) which is relevant to them. For example, you specify that sales organization Florida is to be sent its own target sales quantities but not the target sales quantities of sales organization Texas, and not the total target sales quantities for all sales organizations. You configure distribution models in Customizing for Application Link Enabling.
In order to be able to send the data of a particular information structure, you must have the system generate a message type for it (please see "Activities" below). This ensures that an IDOC containing planning data is transmitted to the receiver whenever the data of this information structure is saved. This may be a sales plan, a production plan, or any planning data saved in an information structure. Previous planning data at the receiver location is overwritten in this process. Thus, if the user wishes to resend data for any reason, he or she must call up the planning data and save it. All message types generated for Sales & Operations Planning have the format "LIPxxx" (xxx stands for the three figures after the leading "S" in the name of the information structure).
At the receiving end, the Workflow Management module records the arrival of an IDOC, checks its date, and ensures that the most recent data is saved. If subsequently it is decided that the older data is needed after all, it has to be sent again.
It is possible to define a line in the planning table such that it is not ready for input, for example, such that the planning figures set centrally cannot be changed decentrally.
Example
- Sales plans are created decentrally by the company's sales organizations and passed to head office. Head office creates an overall production plan based on the cumulated sales plans and then distributes production quotas to individual plants. These, in turn, report their ability to meet these targets back to head office, which adjusts the production quotas accordingly. Reasons why production plants might not be able to meet the central targets include machine failure or a staff shortage. The planning table might contain a line showing the difference between the quotas set by head office and those set decentrally. Because the criteria which determine a sales plan are very different from the criteria which determine a production plan, there is no need for the sales planner and the production planner to communicate directly with each other.
- Alternatively, or in addition, head office may adjust the sales targets set by the individual sales organizations.
Requirements
The information structure must be present both centrally and decentrally so that characteristic values can be recognized on both sides.
Actions
To configure an information structure for use in Application Link Enabling:
- Specify the information structure.
- If you want any existing message type for this information structure to be overwritten by a new message type, set the update indicator. If you want a message type to be created for this information structure only on condition that none existed before, do not set the update indicator.
- Select Enter.
The system now creates a message type for this information structure.
Further notes
To use ALE for Sales & Operations Planning, you must also make a number of settings centrally. For further information, see the Implementation Guide for Application Link Enabling.
Transport Notes
When you execute this transaction, you are required to enter a change request number. This will enable your ALE setting to be transported via a transport request.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-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 | OLIS_ALE | 0 | HLA0006235 | Distribution Requirements Planning |
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 |
| MC7E | T - Individual transaction object | MC7E | 02 | ALE Setting for Information Structure |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
