Kontakt

Ansicht
Dokumentation

RPCSVPD0_IN - SI: Collect and Confirm Results GKV / DSRV

RPCSVPD0_IN - SI: Collect and Confirm Results GKV / DSRV

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

Purpose

Report RPCSVPD0_IN is used to get processing results and qualified confirmations in the following notification procedures:

  • rvBEA (GML57 and rvBEA FORMS including registration)
  • A1
  • Electronic Incapacity to Work (eAU)

After the outbound notification files have been sent using the B2A Manager, the report RPCSVPD0_IN can be started. Note that it can take some time to provide the processing results so these results are not available immediately.

After a test phase, the report can also be started automatically as a job once a day or once a week.

Report RPCSVPD0_IN complements report RPCSVPD0, which should be used for all SI notification procedures not listed above (for example, contribution statement, DEUEV, etc.).

Integration

To query the inbound notification files, the report uses an administration table to select the notification files still open for querying. The processing result is requested on the DRV server or the SHI communication server and evaluated. After successful processing in the SAP system, the processing is confirmed at the server.

The requests, processing results or confirmation files are always queried, retrieved, and processed for each data provider. It is not possible to query the processing result of a particular file number on the server since only the company numbers of the data provider, the fund receiving office, and the type of procedure are determined for the query.

If no selection is made, a list of company numbers and data providers is created for the request for which a valid certificate (PSE file) is available. This is necessary to also retrieve requests from the server that occur in addition to the normal confirmation of processing. (Example: GML57)

Special characteristics of procedure - rvBEA

The rvBEA files are all sent using data type ARV or retrieved using data type RVA. In the B2A manager, the rvBEA files have various document types.

  • rvBEA registration: Outbound file (OREG), inbound file (IREG)
  • rvBEA - GML 57 notification: Outbound file (OG57), inbound file (IG57)
  • rvBEA - FORMS: Outbound file (ORFA), inbound file (IRFE)

This means that the file counter within the document types may show gaps.

Special characteristics of procedure - A1

The A1 files are all sent using data type A1A or retrieved using data type A1S. In the B2A manager, the rvBEA files have various document types.

  • A1 - Request Posting/Exception Agreement: Outbound file (OA1A). Inbound files (IA1A and IA1S)

This means that the file counter within the document types may show gaps.

Special characteristics of procedure - eAU

The eAU files are all sent using data type EAA.

Confirmations for AU data are issued using data type EAR. Error confirmations and forwarding confirmations are issued using data type EAI.

For confirmations, a bundled collection is possible using data type EAS, whereby confirmations for AU data, as well as error confirmations and forwarding confirmations, are collected.

If you do not select the data type or EAR or EAI via the selection screen, a bundled query is implemented via data type EAS.

Prerequisites

The outbound notifications were transferred using the B2A Manager via HTTPS to the DRV using the DRV server or a receiving office using the SHI communication server.

Features

Selection

Start the report without selection. This ensures that all open processing results or confirmations are queried and processed.

The selection parameters are intended for the restriction for individual runs or test runs.

Group box: Notification Selection

  • Company number of receiving office: The company number of the receiving office of the notification file
  • Company number data provider: A company number or a special sender number of the sender from your system. A valid certificate (PSE file) is necessary for creating the connection to the server.
  • Personnel area: Personnel area for which the report retrieve files. (data provider)
  • Personnel subarea: Personnel area for which the report retrieves files. (data provider)
  • Type of data exchange: The data exchange type of the relevant notification procedure
  • Response ID: You can use this to retrieve responses with a larger response ID than what has been specified. For example, if the processing is terminated in the inbound file with response ID '4711' according to the log, they can get the subsequent inbound files by entering response ID '4711' in the selection screen.


Group box: Program Control

  • Additional Functions
    Here you can select one or more additional functions.
  • CONFIRM_ALL: Files that have already been processed (with a file number smaller than or the same as the highest file counter in table T5D4U) are confirmed in a productive run.

    Newly retrieved files are only processed if the file number is greater than the file counter in table T5D4U. These files are then listed in the log statistics as "already processed files".

    This additional function (according to the file counter) also confirms "already processed files" and the files should then no longer be available for retrieving on the server.

  • FORCE_PROCESS: In some SI processes, you can force the saving of data, even if there are errors in the data record structure. As a result, incorrect data can be confirmed.

  • Create Log
    It is not a question of whether or not a log is created, but whether a detailed or a simple log is created. If this checkbox is selected, a detailed log is created using the retrieving procedure, for example with the last file counters from table T5D4U, the XMLs, and the user data received. This is particularly useful for online processing. We recommend that you do not select this checkbox for background processing to make sure that that the log in the spool only contains the most important data and that is not too big. - The XMLs and user data can also be read in the B2A manager when the database is being updated.
  • Database Update
    If this checkbox is selected, all files retrieved are processed, saved (for example, in the B2A manager), and confirmed.

Standard Variants

Output

In the log, the notifications are initially grouped according to the file type. A colored icon (red, yellow, or green) is displayed before the name of the procedure; this icon provides information on the meaning of the notifications for the user in this log branch (see below).

The groupings of combinations of employer company numbers and health insurance company numbers are below the hierarchy level of the process groupings. The type of colored icon here also provides information about the notifications in this log branch.

Colored Icons and Their Meaning:

@5B@ Green icon:
All files in the relevant log branch contain information of little interest for the user.
Examples:

  • Confirmations with processing confirmations

  • Data records are returned

  • Response that no data is available to be retrieved from the server.

@5D@ Yellow icon:
At least one file retrieved in the relevant log branch contains information for the user that needs to be processed in the subsequent process (administrator lists, and so on).
Examples:

  • Quarantine due to different (smaller or same) file number (in comparison to the file counters in view V_T5D4U).

  • Error messages (data module DBFE) for the data sent are returned.

@5C@ Red icon:
At least one notification in the relevant log branch contains an error that needs to be resolved.
Examples:

  • Parser errors

  • Error in the communication process (HTTP)

  • Error during encryption (certificate)

  • Confirmation from the server that a file (file number) has been rejected completely. In this case, also check whether you have imported all existing SAP Notes for the report RPCSVPD0_IN.

Depending on the hierarchy level, an icon refers to files that are a combination of data type, employer company number, and health insurance company number, or to all files for a data type.

Activities

If the confirmations can be stored in the SAP system, this is indicated in the B2A Manager. For this, the following statuses are assigned for the inbound processes:

  • Processing Confirmation - Everything OK
    Inbound process with the status OK/Completed.
  • Confirmation of errors
    Inbound process with the status In Process/Incorrect. The error messages can be processed using the subsequent reports for the application. The status can be set to OK/Completed manually.
  • Confirmation of data records
    Inbound process with the status In Process/Data Records. The data records can be processed using the subsequent reports for the application. The status can be set to OK/Completed manually.
  • File rejection
    Inbound process with the status In Process/Rejection. The receiving office has rejected the complete file. When the error has been resolved, the status can be set to OK/Completed manually.

Comment: During the confirmation of data records and errors, you can use constant AUTCL in table T50BK (view V_T50BK) to set the status OK/Completed.

Special Characteristics of A1

Forwarding Confirmations

When executing this report, error confirmations (file type A1I - document type IA1A) and/or approvals/rejections of A1 requests (file type A1S - document type IA1S) can be collected.

If the transferred data does not result in an error confirmation, a forwarding confirmation for collecting data is provided under the same data type A1I (document type IA1A). The technical transfer of the data was successful in both cases. The relevant outbound notifications are, therefore, set to the status OK/completed.

If it is a forwarding confirmation, the inbound notifications are provided for collection separately with the statements or rejections (data type A1S - document type IA1S) (usually with a delay).

If there is a forwarding confirmation, the processing log with the information that it is a forwarding confirmation is printed instead of the DBFE module in the log display of the corresponding inbound notification in the B2A Manager.

Limitation of Number of Files at DSRV

Due to size restrictions at the DSRV, it is not possible to collect all notifications with one query. In this area, there is usually a maximum of 10 notifications.

At the DSRV, the notifications cannot be separated according to the data type A1A and A1S as is the case at the SHI. This means that all A1 data is always collected during the request for A1A and A1S.

This means that in the report run, it is necessary to transfer the same request to the DSRV several times so that all notifications are collected in one run. This is only possible in the productive run of the report with the database update as otherwise the same 10 files are always collected.

This means that there may be several entries for the same company number for the DSRV with company number 66667777.

This ensures that all notifications are collected during a report run if you should never only select data type A1A or A1S on the selection screen.






TXBHW - Original Tax Base Amount in Local Currency   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 14405 Date: 20240520 Time: 131635     sap01-206 ( 213 ms )