SAP ABAP IMG Activity OALE_DSTSCN_CDLIS (Cumulative Data Transfer)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
MCP2 (Package) R/3 application development: Sales & Operations Planning

⤷

⤷

⤷

IMG Activity
ID | OALE_DSTSCN_CDLIS | Cumulative Data Transfer |
Transaction Code | S_ALR_87008590 | IMG Activity: OALE_DSTSCN_CDLIS |
Created on | 19981222 | |
Customizing Attributes | OALE_DSTSCN_CDLIS | Cumulative Data Transfer |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OALE_DSTSCN_CDLIS |
When aggregated data is exchanged the information is summarized and transported in information structures. It is no longer possible to access single documents in the receiving system.
Activities
If you have opted for aggregated data exchange, proceed as follows:
- Determine the information structure to be used in cumulative data exchange.
- Remember that the characteristic areas between the logistics systems must be mutually exclusive, otherwise data will be overwritten in all directions.
- This is possible, for example, if you:
- Include the logical system in the information structure;
- Carry out derivation using the corresponding standard formula in the SAP Standard System.
- The information structure must be identical in each of the participating systems.
- Afterwards, generate the message type for the information structure. Follow the instructions in the IMG of the Logistics Information Services, section Application Link Enabling (ALE). (Logistics general -> Logistics Information System -> Scheduling -> Functions -> Application Link Enabling (ALE)).
- LIPxxx (xxx = number of information structure, for example, LIP096) is assigned as the name of the message type.
- The IDoc type used is SOPGEN01.
- The message type must be identical in each of the participating distributed systems.
- Specifications in the transmitting systems:
- Determine the copy plan version that is used internally.
- Schedule the "info structure upload" as a periodic
- background job (for example, once a day). You can do this via: Logistics -> Central functions -> Distribution, followed by the menu option Applications -> Logistics information system -> Info structure upload.
- Furthermore, you must define the model, the partner profiles, and so on.
Standard tasks
To ensure that work items are generated should an error arise, you must assign the following standard task to positions or workflow organizational units.
Standard task: ID code Description
SOPGEN_Error SOPGEN Outbound error
Further notes
For more information on the precise steps involved, refer to the Implementation Guides of the Logistics information systems and of Sales and Operations Planning.
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 | OALE_DSTSCN_CDLIS | 0 | HLA0006423 | Logistics Information System (LIS) |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 19990115 |
SAP Release Created in |