Ansicht
Dokumentation
CACS_SEGASS_MIGRATE_BZO - Migration of Segments and Assignments in Portfolio Assignment
CPI1466 during Backup PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Purpose
Migration of segments and/or assignments from segment assignment in the commission system to portfolio assignment
Integration
According to the selection, this program migrates the following objects from the commission system to portfolio assignment:
- Segments
- Assignments between commission contracts and segments
- Segments and assignments from segment assignment
The assignments and segments are created with the current status in portfolio assignment.
If the objects are to be maintained in segment assignment after the migration, and are then to be migrated to portfolio assignment, then all objects that already exist in portfolio assignment are rejected. For this reason, the maintenance of objects after the migration should only take place in portfolio assignment.
Prerequisites
To be able to create assignments and segments in portfolio assignment, the appropriate Customizing settings must have been maintained in portfolio assignment. It is particularly important that segment types and roles are maintained. This migration report does not convert processes (such as the procurement of data from segment assignment for additional commission cases). Additional activities are required for this purpose.
Prerequisite for creating assignments is that both the segment and the assignment object (the commission contracts) already exist in portfolio assignment when this program is executed (you can use the CACS_CTRTBU_MIGRATION_BZO program to migrate commission cases). This means that it is not possible to create segments and assignments simultaneously in test mode.
Features
A test mode is available for creating segments and assignments separately. The log, which you can view after each processing, lists the objects that could and could not (for example, due to missing assignment objects) be created.
In accordance with the standard portfolio assignment scenario, the segments are created in portfolio assignment as the object kind SG (segment) and the object type 0CCS (FS-ICM: Commission contract). In accordance with the portfolio assignment logic, only the active versions of a segment are transferred, rather than the entire history. However, these versions are grouped together in a single version for portfolio assignment. All active versions of the segment are read first. The earliest effective start date (BUSI_BEGIN) and the latest effective end date (BUSI_END) form the effective validity period for the portfolio assignment version.
Assignments can only be created if both the corresponding segments and the assignment objects (in this case commission contracts) already exist in portfolio assignment.
You must take into consideration the following peculiarities: Firstly, in segment assignment you can create various assignments (SEGAGRID) for the same commission contract, the same segment, and the same role. These attributes, together with the types of assignment object (in this case, always 00CC), form the effective key for an assignment between segment and assignment object in portfolio assignment. For this reason you cannot create these assignments in portfolio assignment. This also means that this key is used to merge all assignments in the segment assignment into one single assignment for portfolio assignment. The effective validity of this assignment is determined in the segments (see above).
Secondly, you can assign various commission contracts to an assignment between segment and assignment object. As this is not possible in the portfolio assignment, this assignment is split. This is done by creating a separate assignment for each commission contract. The effective validity of this assignment is defined as for the segments (see above).
When executing the program, you can use methods from the CACS_MIGRATION_BZO BAdI. You can use the ADD_WHERE_CLAUSE_SEGMENTS method to add selection criteria to the standard selections.
In the ADD_CUST_FIELDS_SEG and ADD_CUST_FIELDS_SZO methods you can enhance the fields (that are maintained as default) from portfolio structures for segments (PFO_S_SEGCOMM) and assignments (PFO_S_SZO) before creation in portfolio assignment (for example, if specific attributes have been added to these structures.
To do this, you must implement both methods accordingly.
Selection
If the portfolio assignment is located in a system other than FS-ICM, then the creation takes place using a remote function call (RFC). In this case, you must enter the RFC destination. If no entry is made, then the system presumes that the portfolio assignment runs in the same system as this program.
In order for portfolio assignment to know from which system the objects are to be imported, an appropriate origin entry (ORIGIN) must be made in Customizing for portfolio assignment. The origin name is mandatory here.
Both the segment and segment type attributes are available for selections made according to segments. The assignment ID, assignment role and contract number are also available for the selection of assignments. You can use the ADD_WHERE_CLAUSE_SEGMENTS method from the CACS_MIGRATION_BZO BAdI if you want to use other attributes to make the selection.
The creation is simulated in a test run without data being saved in the database (this is not possible for the simultaneous creation of segments and assignments).
When migrating segments, you can only specify the segment type and segment ID as selection criteria for the selection options.
Standard Variants
The test run indicator is set in the standard setting. We recommend that you execute the migration in test mode first. You should only start the program in production mode if the log shows that the creation was executed without errors.
Output
The log lists which objects could be created without problems, and which objects could not be created.
Activities
We recommend that you proceed as follows:
Create the segments and assignments in separate steps. You can use the test mode for this. Once the corresponding processing is complete, the log indicates whether all objects can be created. If the log shows that problems occurred during the creation, you should clean up these problems before starting an update run.
If this program is executed more than once, then portfolio assignment does not allow you to create the same segments or assignments again.
Example
ROGBILLS - Synchronize billing plans General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 7087 Date: 20240531 Time: 215432 sap01-206 ( 162 ms )
