Ansicht
Dokumentation

CACS_CTRTBU_MIGRATION_BZO - Migration of Commission Contracts to Portfolio Assignment (PFO)

CACS_CTRTBU_MIGRATION_BZO - Migration of Commission Contracts to Portfolio Assignment (PFO)

CL_GUI_FRONTEND_SERVICES - Frontend Services   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Migration of commission contracts to portfolio assignment.

Integration

This program migrates commission contracts in the commission system (FS-CS) to portfolio assignment. Commission contracts are created in portfolio assignment as object kind ZO (assignment object) and object type 00CC (FS-CS: commission contract) according to the standard delivery of the portfolio assignment scenario.

Prerequisites

None.

Features

Based on the logic of portfolio assignment, the complete contract history is not transferred but only the active versions of the commission contract (without any parked versions). However these are grouped into a single portfolio assignment version. First, all active versions of a commission contract are read. The earliest effective start date (BUSI_BEGIN) and the latest effective end date (BUSI_END) of all active versions make up the validity period of the portfolio assignment version.

Two methods of BAdI CACS_MIGRATION_BZO may be used to execute this program. You can use method ADD_WHERE_CLAUSE_CTRTBU_ID if you wish to add your own selection criteria to the standard selection options, for instance to select by your own customer attributes.

You can also make additions to the standard-entry fields of the portfolio assignment structure for assignment objects PFO_S_ZO_0000 in method ADD_CUST_FIELDS_ZO if, for example, you wish to add customer enhancements to the structure.

Both methods should be implemented appropriately.

Selection

If portfolio assignment runs on another system, commission contracts are created via Remote Function Call (RFC). Here you have to define the RFC destination. If no entry is made, the system assumes that portfolio assignment runs on the same system as this program.

A corresponding entry (ORIGIN) has to be made in Customizing for portfolio assignment so that the portfolio assignment system knows the system where the objects originate. Specifying the original system is mandatory here.

The commission contracts of the commission application are selected.

You can select by commission contract number, standard contract number and commission contract partner. If you want to select by other (customer-defined) attributes you may use method ADD_WHERE_CLAUSE_CTRTBU_ID of BAdI CACS_MIGRATION_BZO (see above).

Alternatively, you can create a default segment of object type 0CCS (comission contract) according to the standard portfolio assignment scenario. This receives the effective key of the number of the migrated commission contract.

The test run simulates the creation of commission contracts without any data being written to the database.

Standard Variants

The Test Run indicator is the standard setting. We recommend carrying out the migration in test mode first. Only run the program in productive mode if the log documents no errors.

Output

The log details the commission contracts that were created without errors and those that could not be created.

You may repeat this program any number of times because commission contracts that have already been created cannot be created again. Portfolio assignment does not allow commission contracts to be created twice.






PERFORM Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3577 Date: 20240531 Time: 173413     sap01-206 ( 75 ms )