Kontakt

Ansicht
Dokumentation

RPUD3MD0 - Start Reports of SI Reporting in Distributed Reporting

RPUD3MD0 - Start Reports of SI Reporting in Distributed Reporting

BAL_S_LOG - Application Log: Log header data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Cross-client and cross-system processing of SI messages. Combination of messages from multiple clients/systems in a reporting file.

Integration

The following SI reports can be used in parallel/distributed reporting:

  • RPCDSTD0 (Create DEUEV Notification Files for Immediate Notifications)
  • RPCBMTD1 (Create DEUEV Data Medium for Professionals Pension)
  • RPCBOHD0 (Transfer Notifications to the DASBV)
  • RPCZOHD0 (Transfer of Paying Office Notifications to Health Insurance Funds)
  • RPCEAHD0 (Transfer Reimbursement Notifications)
  • RPCEEHD0_OUT (Create Compensation Benefits Notification Files)
  • RPCRGHD0_OUT (Create rvBEA notification files (registration))
  • RPUD3AD0 (Identification and Deletion of DEUEV Notifications)

Prerequisites

  • The usual prerequisites for parallel and distributed reporting apply. See the documentation for report RPMREP00. In particular, the Customizing settings for the sending personnel areas must be identical in all clients and systems.
    However, separation of personnel numbers is not required.
  • The start client/system contains a variant for the report that is submitted on the RPUD3MD0 selection screen. The report is then started in all clients/systems with this variant. This variant does not need to be in the called clients/systems.
  • As the DEUEV file counter (table T5D4U) is only updated in the start client, the same start client always has to be selected for cross-client and cross-system processing of SI messages.
Changing the start client - without moving over table T5D4U - results in inconsistencies in the file counter and rejection of the message files by the receiving offices.
  • The called reports have to exchange data (date and time of transfer, file counter) with the start client or system. An RFC connection to the start client or system therefore needs to be created with the same name in all called clients. An RFC callback connection needs to be entered in the start variant of the DCR report in hidden parameter P_CBDST (non-visible selection criteria) using a variable from table TVARV.
    Framework program RPUD3MD0 also needs an RFC back connection to the selection screen that is used to call scheduler RPMREP00. The same RFC destination can be used here as in parameter P_CBDST.
  • The SI reports listed above can only be started in parallel/distributed reporting with framework program RPUD3MD0. Starting reports directly with scheduler RPMREP00 causes them to terminate.

Features

Framework program RPUD3MD0 is used to call the actual scheduler for parallel and distributed reporting (RPMREP00).

The report entered on the selection screen is run in all target clients/systems.

The data collected there is analyzed and logged in the start client. For technical information about parallel and distributed reporting, see the documentation for report RPMREP00.

For the various SI reports, the following processing is carried out:

  • RPCD3HD0_OUT (Create DEUEV Reporting Files)
    RPCDSTD0 (Create DEUEV Notification Files for Immediate Notifications)
    RPCBMTD1 (Create DEUEV Reporting Files for Professionals Pension)
    RPCBOHD0 (Transfer Notifications to the DASBV)
    RPCZOHD0 (Transfer of Paying Office Notifications to Health Insurance Funds)
    RPCEAHD0 (Transfer Reimbursement Notifications)
    RPCEEHD0_OUT (Create Compensation Benefits Notification Files)
    RPCBNHD0_OUT (Transfer of SI Contribution Statements)
    RPCBNHD0_OUT (Transfer of BEA Notifications)
    RPCRGHD0_OUT (Create rvBEA notification files (registration))
    RPCRVHD0_OUT (Create rvBEA notification files (registration))
    RPCA1HD0_OUT (Create A1 notification files)
The selected notifications in the target clients are flagged as 'transferred'. The associated TemSe objects with the content of the reporting files are created in the start client however.
This ensures that notifications from different clients that have the same sending and receiving office are written to the same TemSe object or to the same reporting file.
The file counter is increased in the start client.
  • RPUD3AD0 (Identification and Deletion of DEUEV Notifications) and
    RPUSVMD0_FLAG (Flag Social Insurance Notifications)
To flag individual notifications, the report RPUD3AD0 can still be started in the relevant clients/systems. To flag an entire file (combination of sender, receiving office, and file counter), the report must be run with framework program RPUD3MD0 however, as the file counter is not contained in all clients.
Report RPUSVMD0_FLAG should be used to flag entire files and not individual notifications. These can be flagged with the person responsible lists in the various notification procedures.
Using the sender, receiver, file number via the RFC connection (parameter P_CBDST), the reports then retrieve the required transfer data in the start client from table T5D4U, and flag the associated notifications in the target clients/systems.
Flagging a complete data medium run or complete notification file with multiple senders and receiving offices is also possible. To do this, specify the run ID (date/time of data medium run) on the selection screen.

Parameter

Report to be Run

Report Name

Name of the report to run in the target clients/systems.

With Variant

Name of the variant to run the report with. The variant must be in the start client (current client).

Number of Sessions

Number of work processes that the report will be split into in the various clients (parallel reporting).

Systems to be Edited

RFC Connections

RFC connections to the target clients/systems that the report will be started in

RFC Callback Connection

RFC connection from the target clients/systems to the start client.

This RFC connection must have exactly the same name in all target clients/systems. The same RFC connection can be entered as entered in hidden parameter P_CBDST in the DEUEV report.

Process Options

Controls the process and behaviour of the report. For more information, see the documentation for report RPMREP00, under 'Selection'.

Example

You want to group together the DEUEV notifications from the following system with one individual notification file per receiving office and send them from the same sender:

  • System XXX, client 001
  • System YYY, client 001
  • System YYY, client 002

This necessitates the following preparatory steps:

  • Choose a system or client where the file counter will be managed and the notification files created and sent from. This start client can be identical to one of the target clients. In this example, client 001 (system XXX) is also the start client.
  • In transaction SM59 (Display and Maintenance of RFC Destinations), set up RFC connections in the start client XXX(001) to the target clients XXX(001), YYY(001), and YYY(002). These RFC destinations will now be called RFC_XXX_001, RFC_YYY_001 and RFC_YYY_002. As the start client XXX(001) will also be used as the target client, an RFC destination needs to be created for this too.
  • In each of the target clients XXX(001), YYY(001), YYY(002), set up an RFC destination for the callback connection to the start client XXX(001). This "callback destination" must have the same name in all target systems, for example, CB_XXX_001.
  • In the start client, create a variant of report RPCD3HD0_OUT containing the settings to be used to run the report in the target clients. RFC callback connection CB_XXX_01 must be submitted using this variant in hidden parameter P_CBDST. To do this, create a variable (for example, "CBDST") in table TVARV with the value "CB_XXX_01". In the variant maintenance screen for the report, you can assign variable CBDST to parameter P_CBDST by activating the parameter under "Hidden Selection Criteria".
  • Start framework program RPUD3MD0 with report name "RPCD3HD0_OUT" and the name of the variant created earlier. Under "Systems to be Edited", enter RFC connections RFC_XXX_001, RFC_YYY_001, and RFC_YYY_002 for the target clients. As RFC callback connection, you can enter CB_XXX_01.





SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 12343 Date: 20240601 Time: 024627     sap01-206 ( 163 ms )