/ISDFPS/TRANSFER_IT_1957 - Convert Infotype 1957 as Part of Operational/Exercise RelationshipsGeneral Material Data CPI1466 during Backup
This documentation is copyright by SAP AG.
This report is used to convert data of HR infotype 1957 to HR infotype 1985 and to adapt data in HR infotype 1956.
The relevant infotypes are part of the "Defense Forces & Public Security" Enterprise Add-On (EA-DFPS) within the HR Organizational Management framework.
Infotypes in HR Organizational Management describe object attributes (such as organizational units, positions, or persons). Individual records of the attributes for an object are stored in infotype tables HRPxxxx, where xxxx is the infotype number. Some infotypes, "table infotypes," also have one or more records in table HRTxxxx for each record in table HRPxxxx, that is, they are two dimensional.
The infotype adapted in this report, infotype 1956 ("Operation/Exercise"), defines a force element (an organizational unit in the "Defense Forces & Public Security" industry solution) as an operation or exercise. In addition to the attributes (such as category and intensity) that are stored in table HRP1956, this infotype, as a table infotype, also contains definitions of one or more operation/exercise contingents in table HRT1956.
In its table section in table HRT1957, infotype 1957 ("Contingent Assignment") describes the assignment of a force element to one or more operation/exercise contingents, which are described in more detail in the infotype 1956 records of the corresponding operations/exercises.
Infotype 1985 ("Operational/Exercise Relationships") creates a relationship between two force elements or between a force element and a position in an operational/exercise structure. The records therefore determine a hierarchy by defining the superiors and subordinates in the hierarchy. This infotype is not a table infotype, that is, its data is contained in table HRP1985 only.
Since over time it has been established that exactly one table record of infotype 1957 logically describes exactly one relationship in infotype 1985, but that, technically, the two datasets can be brought together only at the expense of system performance, the data in infotype 1957 is stored directly in the relevant record in infotype 1985 as of EA-DFPS 6.00. Infotype 1957 is then obsolete.
The purpose of this report is to convert the data currently stored in infotype 1957 to infotype 1985 during the relevant upgrade. In addition, the last contingent in each operation or exercise (that is, each highest HRT1956 table record of an HRP1956 record) is to be extended to the end of the operational/exercise object.
Since only a few customers currently use the construct for infotype 1957 (none of which use it in production) and because it can usually be assumed that all these customers have imported SP4 of the industry solution IS-DFPS 4.71 before upgrading the industry solution to the Enterprise Add-On EA-DFPS 6.00 (only context in which conversion is required), SAP has not delivered this report as an XPRA, since the data has already been converted. This report is used for the manual conversion of infotype 1957 only if SP4 of the industry solution is not imported before the upgrade of IS-DFPS 4.71 to EA-DFPS 6.00. If the report is run inadvertently once data for infotype 1985 has already been maintained in the application, inconsistencies may arise.
If the report is started, a warning about possible inconsistencies is first output before the system starts converting the data of infotype 1957 to the relevant records in infotype 1985. First, all records of infotype 1957 are determined across all clients. For each of these records, the contingent information about the referenced operation/exercise contingent in the table section in infotype 1956 of the relevant operation or exercise is determined. If the information is not found, a warning about this inconsistency of the initial data is output. The system terminates the conversion of this infotype 1957 record and continues with the next record. If the relevant contingent information is found, the system determines whether the contingent is an operation contingent or exercise contingent on the basis of the infotype 1956 record. If this information cannot be determined, the system outputs a warning and continues with the next record. If the system could determine whether the contingent is an operation contingent or exercise contingent, the relevant relationship between two force elements in infotype 1985 is determined that corresponds to the current record in infotype 1957. The data for infotype 1957 is stored for the relationship. Any dependent relationships to positions are also adjusted. If no relationship can be determined, the system outputs a warning.
Once all infotype 1957 records have been converted, the table record for each last contingent is extended to the end date of the operation or exercise for each operation/exercise definition in infotype 1956. In addition, the record with the highest row number in HRT1956 is determined for each record in HRP1956, and its contingent end date is set to the object end date. If no table row is found, the system outputs a warning about the inconsistency of the initial data.
Once the report has been run, the system outputs the usual log for XPRA in the SAP Memory or on the screen. All messages for this report can be found at level 3 (Info) or 4 (Debug), since no (new) inconsistencies can arise in the dataset as a result of this report. However, the warnings briefly described above display any inconsistencies in initial data that must be dealt with. For this purpose, all warnings have a detailed long text.
Vendor Master (General Section) TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 5764 Date: 20191206 Time: 195406 sap01-206 ( 43 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.