Kontakt

Ansicht
Dokumentation

ISU_COLOGRP_MIGRATION - Migration report for filling colocation groups

ISU_COLOGRP_MIGRATION - Migration report for filling colocation groups

ABAP Short Reference   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this program to:

  • Enter initial colocation group field values in all SAP Utilities tables that are to be used in the SAP Utilities scale-out scenario
  • Migrate existing data
  • Enable your data to use the SAP HANA database scale-out functionality in partitions based on colocation groups.

Integration

Prerequisites

To run this report, you need authorizations for the following objects:

  • S_PROGNAM: You require authorization for the following field values:
  • P_PROGNAM: The current program name

  • P_ACTION: 'SUBMIT'.

Define the number of colocation groups to be used in your system.

To correctly determine colocation group values, you must make the correct Customizing settings under SAP Customizing Implementation Guide → Financial Accounting (New) → Contract Accounts Receivable and Payable → Technical Settings → Settings for Scale-Out.

Maintain the components for which the colocation group usage is to be activated. The report is only executed for these components. If you have activated both components in customizing for Scale-Out, IS-U Billing and IS-U Invoicing, we recommend to run the report for IS-U Invoicing first and then for IS-U Billing (for a better system performance).

Features

You can execute this report for the complete data for a SAP Utilities component (such as Billing or Invoicing) or for a selected subset of tables and data within a component. The parameter settings define the fill process for different tables. This process is triggered in parallel batch processes separated by tables and package sizes (lines within one table which must be processed in a single job step). You can use a parameter to restrict the maximum number of jobs that can run in parallel.

Selection

The selection screen provides the following parameters and selection criteria:

  • Component: Select the SAP Utilities component (Billing [ISUBI], Invoicing [ISUIN]) for which the colocation group field is to be filled in the tables.
Depending on the component you have selected, you select single tables or all tables using checkboxes. The system groups tables with a logical and technical connection.
  • For the Billing component (Block "IS-U Billing"):
  • Tables EANL (Installations), EVER (Contracts), ETRG (Billing Orders), EBISIM (Bill. Mass Simul. Trigger), ETTIFN and ETTIFB (Facts) are grouped together. Since the installation ID is an attribute of these tables and determines the colocation group, you can restrict the lines of the tables in which the colocation group is to be entered to a range of installation IDs.
    Dependencies: If you select table EANL, this also selects all other tables. You can only make entries in the dependent tables.

  • If the table EVER(Contracts) is selected - additionally the contracts after move-in reversal process will be processed for all relevant contracts in the system.

  • ERCH (Billing Document Headers) is a table that can be filled individually. As the installation determines the colocation group indirectly via the assigned contract, you can restrict the lines of the table in which the colocation group is to be entered to a range of contract IDs. Note: Only colocation group fields COLOGRP_INST and COLOGRP_INST_L are filled.

  • Tables DBERCHZ1 - DBERCHZ8 (Billing Line Items, Special Information for Line Items), DBERCHZ (Outdated Table, Line Items), DBERCHV (Consumption History), DBERCHE (Condition Data), DBERCHU (Conversion Steps), DBERCHR (Discounts), DBERCHT (Texts), ERCHO (Outsorting), ERCHP (Analysis Periods), ERCHC (Invoicing/Reversal History) are also grouped together. You can restrict processing to a range of billing document numbers.

For the Billing component, only the installation-related colocation groups COLOGRP_INST and COLOGRP_INST_L are filled.

  • For the Invoicing component (Block "IS-U Invoicing"):
  • EITR (Invoicing Trigger) is a separate group. Using business partner IDs, you can restrict the lines in which a colocation group is to be entered.

  • Table ERCH (Billing Document Headers) is a table that can be filled individually. You can restrict the processing to a range of billing document numbers. Note: Only the colocation group field COLOGRP_BP_TAX is filled.

  • DBERDTAX (Tax Indicator Information for a Print Document), DBERDTAX_ADD (Additional Information for Print Document Tax Indicator) are tables that can be filled individually.

  • Tables ERDK (Print Document/Header Data), DBERDU (Conversion Steps per Billing Line Item), ERDB (Documents for Print Document), ERDO (Outsorting Table for Invoicing), EITERDK (Temporary Data Selection: Invoicing -> Bill Printout), DBERDL (Print Document Line Items), DBERDR (Discount Lines - Print Document), DBERDZ (Individ. Lines - Print Document), ERDTS (Additional Charges and Taxes of a Print Document) are grouped together. You can process tables that have been grouped under a single checkbox individually. You can restrict the processing to a range of print document numbers.

  • Clear Colocation Groups:
    Selecting this checkbox clears the colocation group fields in the selected tables. You cannot restrict the Clear function to specific data in the tables.
  • Technical Settings:
  • Max. No.of Jobs (per Range): Use this parameter to define the maximum number of jobs started for each leading table and its assigned data range. (*)

  • Logon/server group: Use this parameter to restrict execution to a group of application servers, which you can maintain in transaction RZ12.

  • Package Size: Number of entries within a range of IDs (for example, by installation, contract, billing document number, ...) that are processed together as a package within a job. (*)

(*) During processing, the report groups tables that can be handled together ("table group") such as EANL, EVER, ETRG, ETTIFN and ETTIFB. The report creates data packages for all installation IDs selected and then processes each data package in jobs that are executed in parallel. The size of these data packages is defined using the parameter "Package Size".
The "Max. No.of Jobs (per Range)" parameter restricts the maximum number of jobs that run in parallel in a table group - that is to say all tables that belong to the range of installation IDs. Table groups must be processed sequentially. The tables for the installation (EANL, EVER, ...) are processed first, followed by the tables for the contract ID (ERCH), and finally the tables belonging to the billing document ID (for example, DBERCHZ*, DBERCHV, ...).
  • Simulation: Select this checkbox if you do not want to update changes to the colocation group fields in the database and would only like to check which errors might occur in the application log.

  • Detailed Log: Select this checkbox if you want to see detailed information messages in the application log. We do not recommend selecting this checkbox when processing large volumes of data in a productive system.

Standard Variants

Output

The system makes entries in all colocation group fields in the selected tables. The processing steps are documented with messages in the application log (the application log object is IUCOLOGRP_FILL).

Please note: During a move-in reversal, the installation field is cleared in the contract table (EVER). This means that the contract and all its dependent tables no longer have a reference to an existing installation. The report fills these entries with the colocation group value '000000000000'.

In some cases, the colocation group values are not entered in every table line. Examples of these exceptions are:

  • Inconsistent data in a system may occur during a migration phase - for example, if document lines are created (DBERCHZ1) without a related header entry (ERCH).

Activities

If you want to use the SAP Utilities scale-out scenario, you must execute this report to migrate and enter the colocation group in all your legacy data for all tables in the respective components.

The following options are available for migrating data:

  1. Enter all data for billing and invoicing without restriction
  2. Split the data for processing purposes. For example, you can start with installation-related tables, and subsequently select specific installations. Make sure that you migrate all entries in all tables.

Example

  1. Select the "Billing" (ISUBI) component. Select all tables. Do not define a range, so that the system selects all lines in the relevant tables.
  2. Define the maximum number of jobs enabled by your current system (it makes sense to use nearly all existing batch processes).
  3. Select an appropriate package size (packages should provide parallel jobs with enough work).
  4. Deselect the Simulation checkbox.
  5. Execute the report in batch mode and check the application log when all processes are complete.
  6. After the tables for the billing component have been processed, repeat the process for the "Invoicing" component.
  7. Process a smaller data amount for the billing component:
    Select the billing component, select all tables assigned to the installation (EANL, EVER, ETRG, ETTIFN, ETTIFB) and select a range of installation IDs. Enter appropriate technical parameters.
  8. Execute the report and check the log messages.






General Material Data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 11197 Date: 20240531 Time: 062037     sap01-206 ( 205 ms )