Hierarchy
⤷ PY-DE-NT-NI (Application Component) Social Insurance
⤷ P01S (Package) HR Germany: Social Insurance
Basic Data
Data Element | P01_D3STATUS |
Short Description | DEUEV Status Indicator |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | P01_D3STATUS | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Status |
Medium | 15 | Status |
Long | 20 | Status Indicator |
Heading | 17 | Status Indicator |
Documentation
Definition
This field displays the status of the DEUEV notification.
Use
The notification status indicates the extent to which that notification has already been processed, as well as which other actions are possible or necessary.
Dependencies
The status that a notification can have depends on the procedure (inbound or outbound) and the type of notification.
Status Indicators for Outbound Notifications (Employer to Health Insurance Fund)
- New (00)
The notification has been created without errors by the report Create DEUEV Notifications (RPCD3VD0) but has not yet been processed further.
- With Errors (12)
The notification could not be created without errors by the report Create DEUEV Notifications (RPCD3VD0) (see error log). Correct the error and restart the report so that the notification receives the status New.
If you cannot correct the error, report the notification manually and use the report Administrator List for DEUEV Notifications (RPCD3LD0_OUT) to set the status of the notification to Reported Manually.
- Transferred (01)
The notification has been written to a TemSe file by the report Create DEUEV Notification Files (RPCD3HD0_OUT) and forwarded to the B2A Manager (transaction PB2A).
- Rejected (10)
This notification was transferred to the receiving office, where it was rejected. The following reports can set the status Rejected:
- Administrator List for DEUEV Inbound Notifications (RPCDRLD0)
- The receiving office sends an error confirmation (inbound notification) to reject the outbound notification. You can use this report to process the error confirmation and set the status of the outbound notification to Rejected. The status of the error confirmation is changed from To Be Rejected to Processed.
- Administrator List for DEUEV Notifications (RPCD3LD0_OUT)
- You can use this report to set the status of an outbound notification from Transferred to Rejected. Only use this option if it is not possible to process the error confirmation for any reason.
- Reported Manually (13)
You can use the report Administrator List for DEUEV Notifications (RPCD3LD0_OUT) to set this status. It states that the notification has been reported manually to the receiving office and may no longer be processed automatically.
The Reported Manually status can be set only for notifications with the status With Errors or Rejected.
Status Indicators for Inbound Notifications
- Received (20)
The B2A Manager has received the notification and stored it in the system, but has not yet processed it further. Using the report Assignment of DEUEV Inbound Notifications (RPCDRHD0), the notification is now to be assigned to a personnel number. The possible status indicators are To Be Rejected, To Be Noted, To Be Processed, and Not Assigned.
- To Be Rejected (21)
This status can only occur when error confirmations are sent by the receiving office. It indicates that the error confirmation could be assigned to an outbound notification successfully using the report Assignment of DEUEV Inbound Notifications (RPCDRHD0).
In the next step, the error confirmation is to be set to the status Processed using the report Administrator List for DEUEV Inbound Notifications. In doing so, the status of the outbound notification to be rejected is simultaneously changed from Transferred to Rejected.
- To Be Processed (22)
This status can only occur when the pension insurance number is confirmed or when confirmations are sent to the employer (DSKK inbound notifications). It indicates that the notification could be assigned to a personnel number successfully using the report Assignment of DEUEV Inbound Notifications (RPCDRHD0).
In the next step, the notification needs to be processed further by the report Process DEUEV Confirmations (RPCDRVD0).
- To Be Noted (25)
This status can only occur when information notifications are sent by the receiving office. It indicates that although the receiving office has processed and forwarded the DEUEV outbound notification, the receiving office needed to inform the employer of special circumstances in conjunction with this notification.
So, the DEUEV outbound notification was accepted, but the employer is to take note of some information. After you have taken sufficient note of the information, you can use the report Administrator List for DEUEV Inbound Notifications (RPCDRLD0) to set the status of the information notification to Processed Manually.
- Rejected by Employer (30)
This status indicates that an inbound notification contains data that is incorrect from a technical perspective such that the report Process DEUEV Inbound Notifications (RPCDRVD0) could not interpret and process this inbound notification. Therefore, it was rejected by the employer, meaning excluded from processing.
- Not Assigned (34)
This status indicates that the inbound notification could not be assigned correctly via the report Assignment of DEUEV Inbound Notifications (RPCDRHD0). Possible causes:
- For error confirmations or information notifications
- No associated personnel number could be determined or the outbound notification to which the error confirmation/information notification refers was not found.
- For PI number confirmations or confirmations to employer
- No related personnel number could be determined.
The following status indicators can occur during further processing of a successfully assigned inbound notification:
- Processed (23)
This status indicates that the inbound notification was processed automatically and is therefore "Completed". No further status changes are possible. This status is set by the following reports:
- In case of error confirmations:
- The notification was processed via the report Administrator List for DEUEV Inbound Notifications (RPCDRLD0) and the status of the related outbound notification was set to Rejected.
- In case of PI-number confirmations:
- The notification has been processed successfully using the report Process DEUEV Inbound Notifications (RPCDRVD0).
- In case of confirmations to the employer (DSKK inbound notifications)
- The notification has been processed successfully using the report Process DEUEV Inbound Notifications (RPCDRVD0).
- To Be Checked (32)
This status can only occur when the PI number is confirmed or when confirmations are sent to the employer (DSKK inbound notifications). It indicates that an error occurred during processing using the report Process DEUEV Confirmations (RPCDRVD0).
If you are able to correct the error, restart the report. Otherwise, process the notification manually and use the report Administrator List for DEUEV Inbound Notifications (RPCDRLD0) to set the status of the notification to Processed Manually.
- Processed Manually (33)
This status indicates the inbound notification could not be automatically processed without errors and was therefore processed manually.
It can be set via the report Administrator List for DEUEV Inbound Notifications (RPCDRLD0) for the following inbound notifications: - Error confirmations with the status Not Assigned
- Information notifications with the status To Be Noted
- In this case, the status merely indicates that the information has been taken note of and is therefore 'completed'.
- PI-number confirmations with status To Be Checked
- Confirmations to the employer (DSKK confirmations) with the status To Be Checked
Example
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |