Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE-PS (Application Component) Public Sector⤷
P01O (Package) HR Germany: Public Sector
IMG Activity
| ID | OHADOE_ZFA_010 | Status Management - Overview |
| Transaction Code | S_L7D_24001518 | (empty) |
| Created on | 20080201 | |
| Customizing Attributes | OHADOE_ZFA_000 | ZfA Notifications |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADOE_ZFA_010 |
Status Management for ZfA Notifications
ZfA status management logs the arrival and output of ZfA notifications. It must be activated before B2A data exchange with ZfA can be started.
Status Management in the Outbound Process:
- When the ZfA notifications are created using reports
- Create ZfA Notifications BZ01 -RPCZFAD0_BZ01
- Create ZfA Notifications BZ02 -RPCZFAD0_BZ02
- Create ZfA Notifications KZ01 -RPCZFAD0_KZ01
- Create ZfA Notifications KZ02 -RPCZFAD0_KZ02
entry "Created" is written to status management for each notification created if status management is active.
- The XML files are no longer created at the same time as the notifications, but instead in a separate report (Outbound ZfA Notifications -RPCZFAD0_OUTBOUND). This report collects the notifications with status "Created" and converts them to XML files. The notifications are then assigned status "Collected".
- The XML files are sent to the B2A outbound directory. At the same time, a B2A process is generated that can then be started in the B2A Manager.
- Once the B2A transfer is complete, the notifications are assigned status "Transferred".
Example: Status history of notification 00029029 BZ01 00001
PersNo Reasn Not.No. No Status Date Time Report Field Name
29029 BZ01 00001 1 Created 11/08/2007 14:31:29 RPCZFAD0_BZ01
29029 BZ01 00001 2 Gesammelt 11/08/2007 14:37:44 RPCZFAD0_OUTBOUND
29029 BZ01 00001 3 Transferrd 11/09/2007 10:53:20 H99_B2AMANAGER
Notifications that have been transferred using the B2A Manager can be collected and transferred again by assigning them status "Recollect" (ZfA Cluster Display/Auxiliary Program - RPUZFAD0). The same applies to notifications that were stored in a PC outbound directory using the old procedure and transferred from there to the ZfA.
Example: Status history of notification 00029029 BZ01 00001
PersNo Reasn Not.No. No Status Date Time Report Field Name
29029 BZ01 00001 1 Created 11/08/2007 14:31:29 RPCZFAD0_BZ01
29029 BZ01 00001 2 Collected 11/08/2007 14:37:44 RPCZFAD0_OUTBOUND
29029 BZ01 00001 3 Transferrd 11/09/2007 10:53:20 H99_B2AMANAGER
29029 BZ01 00001 4 Recollect 11/21/2007 18:41:00 RPUZFAD0
29029 BZ01 00001 5 Collected 11/25/2007 15:59:26 RPCZFAD0_OUTBOUND
29029 BZ01 00001 6 Transferrd 11/26/2007 08:12:47 H99_B2AMANAGER
The ID of the XML file (ZFA-ID) and the B2A process (GLBID) are also stored in status management along with an indicator of whether the data is test data (TESTD). The IDs of the file and the B2A process are generated automatically, and the test data indicator is determined based on the test/live indicator of the client and can be overridden by B2A constant MODE (view V_T50BK , personnel country grouping 01, area OED).
Status Management in the Inbound Process:
If status management is active, entry "Received" is written to status management in Processing of All Notifications in Inbound Directory - RPCZFAD0_INBOUND for each notification that is processed.
Example: Status history of notification 00029054 ZK01 00001
PersNo Reasn Not.No. No Status Date Time Report Field Name
29054 ZK01 00001 1 Received 11/09/2007 14:12:08 RPCZFAD0_INBOUND
If the inbound directory contains outbound notifications that have been rejected by the ZfA due to errors in structure or content, entry "Rejected" is stored in the status management of the original notification.
Example: Status history of notification 00029012 BZ02 00001
PersNo Reasn Not.No. No Status Date Time Report Field Name
29012 BZ02 00001 1 Created 11/08/2007 14:35:17 RPCZFAD0_BZ02
29012 BZ02 00001 2 Collected 11/08/2007 14:37:44 RPCZFAD0_OUTBOUND
29012 BZ02 00001 3 Transferrd 11/09/2007 10:53:20 H99_B2AMANAGER
29012 BZ02 00001 4 Rejected 11/09/2007 14:12:06 RPCZFAD0_INBOUND
Status Management and the Further Processing of Notifications:
The further processing of ZKO1 and ZB01 notifications of the ZfA was controlled by processing indicators even in the old programs (FBZ02 and FZB01). These indicators are stored in the cluster data record of the notification, but without a history. They are still written after status management has been activated. The status history is written to the new status management in parallel.
Example: Status history of notification 00029054 ZK01 00001 (received and answered by KZ01)
PersNo Reasn Not.No. No Status Date Time Report Field Name
29054 ZK01 00001 1 Received 11/09/2007 14:12:08 RPCZFAD0_INBOUND
29054 ZK01 00001 2 Completed 11/10/2007 08:12:37 RPCZFAD0_KZ01
Example: Status history of notification 00029013 ZB01 00001 (received and infotype updated)
PersNo Reasn Not.No. No Status Date Time Report Field Name
29013 ZB01 00001 1 Received 11/09/2007 14:12:07 RPCZFAD0_INBOUND
29013 ZB01 00001 2 Processed 11/09/2007 14:25:32 RPUZFAD0
Example: Status history of notification 00029013 BZ02 00001 (answered by ZB01 above)
PersNo Reasn Not.No. No Status Date Time Report Field Name
29013 BZ02 00001 1 Created 11/08/2007 14:35:18 RPCZFAD0_BZ02
29013 BZ02 00001 2 Collected 11/08/2007 14:37:44 RPCZFAD0_OUTBOUND
29013 BZ02 00001 3 Transferrd 11/09/2007 10:53:20 H99_B2AMANAGER
29013 BZ02 00001 4 Answered 11/09/2007 14:12:07 RPCZFAD0_INBOUND
Status Management and the Deletion of Notifications:
If a notification is deleted in ZfA Cluster Display/Auxiliary Program - RPUZFAD0, all entries for this notification are also deleted from status management.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20080201 |
| SAP Release Created in |
