Hierarchy
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ CACS1D (Package) ICM: DDIC for ICM Basis Technology Package
Basic Data
Data Element | CACSPACKAGE |
Short Description | Pakage ID in Incentive & Sales Force Management |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CACSPACKAGE | |
Data Type | CHAR | Character String |
Length | 6 | |
Decimal Places | 0 | |
Output Length | 6 | |
Value Table | TCACS_PACKDEF |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Package |
Medium | 15 | Package |
Long | 20 | Package |
Heading | 8 | Package |
Documentation
Definition
In Incentive and Sales Force Management (ISF) you determine the type and scope of your application through the selection of ISF packages.
An ISF package is a container for objects that belong together either functionally or technically. Unlike normal development packages, ISF packages can contain Customizing objects as well as development objects. They contain repository objects, client-specific and cross-client configuration, as well as master data and transaction data.
Depending on their intended usage, ISF packages a larger or smaller number of repository objects, and so on. A repository package of SAP NetWeaver AS always serves as a technical container for the repository of a package.
There are no restrictions for the contents of ISF packages that are intended for IDES, for example. On the other hand, technical and architectural model packages are restricted to repository and cross-client Customizing.
The use of a package depends on the business objects that are relevant for creating or enhancing scenarios, processes and process steps. The usage can vary from pure application design through production configuration to demo content.
ISF packages serve as templates from which you can construct your application. There are two types of ISF packages: core packages and enhancements packages.
Core package:
Each application contains a single core package that determines the type of application and thus the functional orientation of an application.
Enhancement package:
Enhancement packages require at least one additional package (core or enhancement package).
Many enhancement packages can be combined and are compatible, whereas others are mutually exclusive. The choice of enhancement packages determines the scope of the application and the level of preconfiguration.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 462 |