Ansicht
Dokumentation
HMXUACTPBS_CE - Personnel action report
ROGBILLS - Synchronize billing plans TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Purpose
Government employers must notify an authority, such as ISSSTE, all events occurred in their institution concerning changes in monthly basic quotation wage (BQW) of employees who are obligated to contribute to the authority. These events, or actions, to be considered are categorized into three types: hiring, termination and change in pay event. The notification to be sent to the authority is in the form of three separate magnetic files, one file for each type of event. This program finds events and generates the magnetic files containing information about them.
After the magnetic files have been generated, they will be sent to the authority. Via the file, the authority is notified of any hiring, termination and change in pay affecting the monthly BQW of employees in the institution.
Hiring and termination events are detected through infotype 0000 Actions and infotype 0369 Social Security Data; Change in pay events are detected through infotype 0008 Basic Pay, 0014 Recurring Payments/Deductions and 0015 Additional Payments and table T7MX62 'Minimum wages of economic zones'.
Prerequisites
COMPLETE IMG STEPS
1. Set up feature for mapping of hiring and termination action type in infotype 0000 Actions to ISSSTE-defined action type.MXACT: ISSSTE Action Type
2. Set up feature for mapping of appointment type field value to the value to appear in magnetic file.MXAPP: ISSSTE Appointment Type
3. Implement BADI for ISSSTE Action Report - Salary, if the method of calculating salary to be used in the basic quotation wage calculation for ISSSTE, SAR and total salary for the institution is different from the default method the report provided which uses the sum of wage type amounts from infotype 0008, 0014 and 0015. See the documentation of BADI HRPBSMX001 (BADI for ISSSTE Action Report - Salary) for more information.
4. Implement BADI for ISSSTE Action Report - Charge Code, if the method of forming the charge code for the enterprise is different from the default method provided by the report. The default charge code takes its value from the object abbreviation of employee's job (infotype 0001 field STELL), if exists. Otherwise, it takes the value of employee's job title. See the documentation of BADI HRPBSMX002 (BADI for ISSSTE Action Report - Charge Code) for more information.
3. Create additional entries in table T539J for valuated wage types ISAL, SSAL and TSAL, as appropriate. ISAL, SSAL and TSAL are valuated wage types for basic quotation wage for ISSSTE, SAR and for total salary, respectively.
It is important to note that the same set of wage types specified in payroll and in the processing class to be defined and the wage types forming the basis of ISSSTE and SAR contribution calculation and total salary must be all specified here in table T539J as well.
See also IMG steps "Payroll: Mexico/Suplementos sector publico Mexico/Seguridad social/Configuracion del reporte de Movimientos Afiliatorios ISSSTE".
UPLOADING OF HISTORICAL DATA
,,Before the first execution of the program HMXUACTPBS, the upload program HMXUUAHPBS must have been successfully executed in real mode once to upload all historical actions into databases which will be used later by the program HMXUACTPBS.
,,See documentation of the program HMXUUAHPBS for more information.
WAGE TYPES FOR THE CALCULATION OF BASIC QUOTATION WAGE AND TOTAL SALARY
,,In the system, wage types ISAL, SSAL and TSAL must exist. They are valuated wage types forming from base wage types present in infotypes 0008, 0014 and 0015. These valuated wage types are used in the program for the calculation of basic quotation wages for ISSSTE, SAR and total salary, respectively. Base wage types forming valuated wage types ISAL, SSAL and TSAL must have been specified previously in table T539J.
Note that it is important to have the same set of base wage types both in calculation of contribution basis in payroll and in the table T539J for ISAL, SSAL and TSAL valuated wage types used in this report, where ISAL is equivalent to basis for ISSSTE contribution, SSAL to basis for SAR contribution and TSAL to total salary.
INFOTYPE RECORDS FOR EMPLOYEES
,,Each magnetic file contains certain required and non-required data from employee's infotype records. When the report is run, it will process one or more employees. If required data of one employee are missing, the absence is treated as an error and the magnetic file containing action record of that employee will not be generated in real mode when running the report. If the non-required data are missing, the absence will only generate warnings and the magnetic file will be generated, in real mode running. Note that all three types of magnetic files are generated in one same program run, when the run is in real mode and with no errors in all magnetic files. If one magnetic file has errors and is not being generated as a result, this will prevent other magnetic files from being generated as well.
Note that to be considered for processing by the report, as a minimum, an employee must have infotype 0369 'Social Security Data'. All employees with no infotype 0369 record will be rejected by the report, i.e. no further processing for the employee. If the employee has infotype 0369 record, only those hiring, termination and change in pay events that occurred when the infotype 0369 obligation status of the employee is not of type 'Exempt from Contribution Obligation' will be processed. Furthermore, only those events that occurred while the employee has an active employment status are considered.
Selection
SELECTION SCREEN OF THE REPORT
Note that when the button 'Read TemSe File' on the selection screen is selected, not all the fields of the selection screen are available to the user. To get back the full set of fields again, the user will push the button 'Save as TemSe'.
Time period
-----------------
The time selection parameter on the selection screen represents the time period during which if the infotype records of the employee are available. The employee will be processed.
Person selection
----------------------
Personnel number to be processed is specified in the person selection of the selection screen, which also contains additional person selection parameters such as payroll area. Other person selection parameters can be found under 'Further selections'. If no person selection criteria are specified, all employees are selected.
Temporary Sequential File (TemSe)
----------------------------------
A TemSe is used to save the results of the program execution. When executing the program, the user has two choices regarding saving to a TemSe file. One option is to execute the report to find all actions and then save results into a TemSe file. Another is to execute the program only to display the results of an earlier execution of the report which were saved in a TemSe.
To save the results in a TemSe file, the user will select the button 'Save as TemSe' on the selection screen, before executing the program. In the TemSe file name that appeared, the user will enter the name of the TemSe file destination.
To read from a TemSe file, the user will push the button 'Read TemSe File' on the selection screen, before executing the program. In the TemSe file name that appeared, the user will enter the name of the TemSe file to be read from.
Branch code name
------------------
If entered here, branch name text will later appear in the header of consolidated list output of the report. Example of branch code name is: 'BRANCH CODE: 09120 CAMINOS Y PUENTES FEDERALES. Also see section 'OUTPUT' of this document.
Notification date
---------------------
Certain information about an action record reported to ISSSTE is kept in database tables used by the report. Among the information kept, notification date is one of them and its value is specified here on the selection screen by the user when running the report. Notification date is the date the magnetic files being generated will be sent to ISSSTE. There is no restriction on the value entered for this date and it will not appear in any output of the program. In test mode running of the report, notification date is not needed.
Test mode or real mode running
--------------------------------------------
The report can be run in test mode which means magnetic files will never be generated and databases will not be updated. In real mode, only when no errors exist, magnetic files will be generated and databases will be updated.
If the report finished running with errors, no magnetic files will be generated regardless of whether the report was run in test or real mode. To run the report in test mode, check the check box. To run in real mode, uncheck it.
Note that in real mode, if errors exist for a type of action, not only that the magnetic file of that action type will not be generated but magnetic files of other action types will not be generated as well, even when other action types do not have errors themselves. In effect, in real mode, all files will be generated at the same time when all action type processing contain no errors.
The user can save results to a TemSe file in both test or real mode running, and also in online run or background processing. In background execution, saving to a TemSe file is mandatory. If the program is run online and in real mode, supplying names of the magnetic tapes are mandatory, regardless of whether the results are being saved to TemSe or not.
Note that if the user executes the program in test mode, where no databases would be updated, and saves the result into a TemSe, then that TemSe can only be read back in test mode. Since, in real mode, the user intends to generate the magnetic files, the TemSe that was generated in test mode cannot be used later on to generate magnetic files. Only TemSe file generated in real-mode execution can be used later to generate magnetic files.
File name
-------------
The file name refers to the file name of the output magnetic file. In real mode, because the magnetic files will be generated, the file names are required. In test mode, however, supplying names are not mandatory since in test mode no magnetic tapes will be generated anyway.
Renotification selection
------------------------------
Records which have been included once in a magnetic file can be processed and reported to the authority such as ISSSTE again. If it is decided that the report should process as well previously reported actions, the Renotification check box should be checked on the selection screen. If this check box is unchecked, only records which have never been included in magnetic files will be processed when the program runs. Note that when the check box is checked, both the previously reported actions and actions which have never been reported previously will be processed.
Include change in minimum wage
---------------------------------------------
Change in basic quotation wage can originate from change in pay in master data records (infotype 0008, 0014 and 0015) and from change in daily minimum wage for economic zone A in table T7MX62. Check this box. If changes originated from the later source must be reported to ISSSTE as well as the former. If the box is unchecked, the change originated from the later will not be reported while the change from the former will be. Note that if the change originated from the minimum wage should be considered, employees affected are only those with basic quotation wage equals to basic quotation wage calculated from minimum wage.
INFOTYPE RECORD SELECTION
Hiring and termination action events are selected from infotype 0000 Actions and infotype 0369 Social Security Data.
Mapping of action type in infotype 0000 Actions to ISSSTE-defined hiring and termination action type is done through feature MXACT. A change of infotype 0369 obligation status from 'Exempt from Contribution Obligation' to either 'Subject to Contribution Obligation' or Subject to Contribution Obligation without a number' is a hiring event. A change of infotype 0369 obligation status from 'Subject to Contribution Obligation' or 'Subject to Contribution Obligation without a number' to 'Exempt from Contribution Obligation' is a termination event.
Hiring and termination action events will be selected from infotype records according to the following rule.
1. For events with start date of the record earlier than the date the record was entered in the SAP system, the event will be selected if the date the record was entered in system is in between time selection period on selection screen.
2. For events with start date of the record later than the date the record was entered in the SAP system, the event will be selected if the start date of the record is in between time selection period on selection screen.
Change in pay action events are detected from changes in basic quotation wages calculated from employee's records in infotype 0008 Basic pay, 0014 Recurring Payments and Deductions and infotype 0015 Additional Payments of the employee and also from changes in table T7MX62.
Time period used in the selection of change in pay events has, as the begin date, the earliest date of the following.
1. The start date of payroll period of the begin date from the selection screen.
2. The earliest master data change since last payroll run.
In the case the start date of payroll period of the begin date from the selection screen is not available, the begin date from the selection screen is taken in stead. In the case that the earliest master data change has no value, the system low date is used instead.
The end date of the time period used in selection of change in pay events is taken as the end date from the selection screen.
Change in pay action event will be selected if the date of change in pay falls in between time period derived above.
The 'date of change' for change in pay action events from infotype 0008 and 0014 is the date at which the change in pay occurs. The date of change for change in pay action events from infotype 0015 is the start date of the payroll period in which the change in pay falls into and the start date of the next payroll period. For example, if a new infotype 0008 record causing a change in pay has the start date of the record on 1.1.2003 then, the date of change of this change in pay action event is 1.1.2003. On the other hand, if a new infotype 0015 record causing a change in pay has the date of origin of 3.1.2003, there will be two changes in pay action events generated by this infotype 0015 record with date of change of 1.1.2003 and 16.1.2003, assuming semi-monthly.
Besides existing infotype 0000 Actions and infotype 0369 Social Security Data records, deletion of master data records of infotype 0369 can also generate hiring and termination action events. In the event that an infotype 0369 record which was previously reported to ISSSTE as a hiring (termination) has been deleted, an action type record of type termination(hiring) will be generated for the magnetic file of type termination(hiring), when either one of the following conditions are fulfilled.
1. If no other infotype 0369 record of same action type as that of the deleted record can be found with the last changed date on or later than that of the deleted record.
2. If another infotype 0369 record of the same action type as that of the deleted record can be found with the last changed date on or later than that of the deleted record and with the start date later than that of the deleted record.
FIELD VALUES IN OUTPUT MAGNETIC FILES
In the following, the most current infotype record available refers to the most current record within time selection period specified on the selection screen.
1. LAST NAME, SECOND LAST NAME, FIRST NAME, FEDERAL TAXPAYER REGISTRATION NUMBER, GENDER, STREET, EXTERIOR AND INTERIOR NUMBER (apartment number) AND ZONE WHERE THE EMPLOYEE LIVES, BIRTH STATE CODE, CURP NUMBER, BIRTH DATE: take values from the most current infotype record available.
2. HIRE DATE, TERMINATION DATE AND SALARY CHANGE DATE: take value of the date the hiring, termination or change in pay occurs. These dates are referred to as 'action date'.
3. MONTHLY BASIC QUOTATION WAGE FOR ISSSTE, SAR AND TOTAL SALARY: take value calculated for the action date.
4. APPOINTMENT TYPE, BRANCH CODE, PAYING AGENT AND CHARGE CODE: take values from infotype record which the action date falls into.
5. ISSSTE NUMBER: take values of ISSSTE number from the most current infotype 0369 record in case the record has obligation status of 'Subject to Contribution Obligation' or 'Subject to Contribution Obligation without a number'. The field takes value of ISSSTE number from infotype 0369 record prior to the most current record in case the most current record has obligation status of 'Exempt from Contribution Obligation'.
Apartment number, ISSSTE number, CURP number and birth date fields are not required fields, while all others are.
In program HMXUACTPBS, absence of required fields is treated as error. Absence of non-required fields generates warning messages.
Output
Outputs of the report are as follow.
1. Magnetic files
There are three separate output magnetic files: hiring, termination and change in pay event. In test mode, no magnetic files are generated. In real mode, all magnetic files are generated at the same time when all action type processings contain no errors. Among the three files to be generated, any file with no contents will not be generated.
2. Output screen
There are three separate list output screens for hiring, termination and change in pay action type and one screen for consolidated list. The data in the list output screens are, partly, duplications of those in magnetic files. The consolidated list shows the number of action records processed for each action type and also the total number of action records processed by the report. By default, the consolidated list will be the first screen to appear. The other screens can be accessed using the hiring, termination and payment modification buttons of the menu bars of the screen.
Note that hiring, termination and change in pay buttons are visible only when the corresponding output list contains records.
In the list output screens for an action type, all entries shown are those processed by the program for the corresponding action type. The data in one line item are personnel number, renotification status (renotified or first notification) and processing status of the record (errors/warnings/no errors) and the same set of data that would appear in the output magnetic file for that entry. Also see section FIELD VALUES IN OUTPUT MAGNETIC FILES in this document.
As an alternative, double clicking anywhere on the line item for magnetic file type 'HIRING', 'TERMINATION' or 'CHANGE IN PAY' in consolidated list output screen will also take the user to the list output screen for hiring, termination and change in pay, respectively.
3. Error log
For each action type, if errors or warnings exist, the error log will be filled with error or warning information. The log can be accessed through the error log button on the menu bar. The button will appear on the menu bar only when there are errors or warnings for that type of action. Each action type has separate error log. If it does appear, the button for each action type error log will appear next to the button for the action's list output screen on the menu bar.
Note that error log from the menu bar is the summary of errors from all personnel numbers, for a particular action type. However, double clicking a line item in the action list output screen will take the user to an error message screen showing only error or warning messages associated with the line item.
4. TemSe file
A TemSe file contains data to be used for displaying of output screens and, if relevant, data to be downloaded to magnetic tapes. The user can write to a TemSe file and to magnetic tapes in the same program execution. Or, he can choose to just write the data out to a TemSe without generating magnetic tapes. Generating a TemSe file is independent of whether the program is run in test or real mode and in online or background execution, except that saving to a TemSe is mandatory in background execution. Only the TemSe file which was generated in real mode can be used later to generate magnetic tapes.
Activities
Execute the report with appropriate selection screen parameters, as explained in the SELECTION SCREEN section above.
Example
In the following, BQW refers to basic quotation wage. Commissions and punctuality bonus are assumed to be a part of BQW for ISSSTE. 'Subject to' is short for 'Subject to Contribution Obligation' and 'exempt' is short for 'Exempt from Contribution Obligation'.
Case 1: report hiring for new hire
An employee is hired on 1.1.2003 with infotype 0369 status of 'subject to'. The date the hiring date was entered into the system is 31.5.2003. The report is run to report the hiring with key date 31.5.2003. A hiring record appears in the hiring magnetic file with start date 1.1.2003.
Case 2: report termination from change in infotype 0369 obligation status
The same employee now has his infotype 0369 status changed from 'subject to' to 'exempt' starting from 16.1.2003. The change is recorded in the system on 1.6.2003. The report is run to report this change as a termination action. The time selection period entered is 1.6.2003. A termination record for this change appears in the termination magnetic file with start date 16.1.2003.
Case 3: report hiring from change in infotype 0369 obligation status
The same employee now has his infotype 0369 status changed from 'exempt' to 'subject to' starting from 1.2.2003. The change is recorded in the system on 2.6.2003. The report is run to report this change as a hiring action. The time selection period entered is 2.6.2003. A hiring record for this change appears in the hiring magnetic file with start date 1.2.2003.
Case 4: report change in pay from change in infotype 0008
The same employee now has change in salary. New infotype 0008 record is created with start date 1.2.2003 and with new wages of 1,600 MXN. The report is run with time selection period of 1.1.2003-1.2.2003 to report this change in pay. A record for this change is created in change in pay magnetic file with start date 1.2.2003.
Infotype 0008 amount start date end date
Employee wages 1,500 1.1.2003 31.1.2003
Employee wages 1,600 1.2.2003 31.12.9999
Magnetic file record
Start date BQW for ISSSTE
1.2.2003 1600
Case 5: report change in pay from infotype 0014 Recur. Payments/Deds.
The same employee received punctuality bonus starting from date 5.2.2003 to 28.02.2003. The report is run with time period of 1.1.2003-1.3.2003. Two records are created in change in pay magnetic file for this change with the start date 5.2.2003 and 1.3.2003, respectively. In this example, we assume the amount of 700 MXN is for semi-monthly.
Below, the amount 3,000 is the sum of the amount 1,600 MXN from Case 4 and the amount 1,400 (700 x 2) from new infotype 0014 record.
Infotype 0014 amount start date end date
Punctuality bonus 700 5.2.2003 28.2.2003
Magnetic file record
Start date BQW for ISSSTE
5.2.2003 3000
1.3.2003 1600
Case 6: report change in pay from infotype 0015 Addition Payments.
The same employee received commissions with date of origin 18.2.2003. The report is run with time period of 1.1.2003-1.3.2003. In this example, we assume the amount of 500 MXN is for semi-monthly.
Below, the amount 4,000 is the sum of the amount 3,000 MXN from Case 5 and the amount 1,000 (500 x 2) from new infotype 0015 record. Notice that the start dates of the magnetic file records are 16.2.2003 and 1.3.2003 which are the start date of the payroll period the date of origin falls into and the start date of the next payroll period.
Infotype 0015 amount date of origin
Commissions 500 18.2.2003
Magnetic file record
Start date ISSSTE BQW
16.2.2003 4000
1.3.2003 1600
Case 7: report termination from infotype 0000 Actions.
The same employee left the enterprise on date 31.12.2003. The record was entered in infotype 0000 with action type 'leaving', on date 1.12.2003 with start date 31.12.2003. The report is run to report this termination with key date 31.12.2003. One termination record is created in the magnetic file with the start date 31.12.2003.
Exceptions
,,GENERATION OF MAGNETIC FILES
The user has two choices to generate magnetic files. One is to generate magnetic files in the same program run that finds actions. Another is to generate magnetic files in a separate program run from the run that finds the actions. In the second option, the user save the results of the first program execution to a TemSe file and read back in a separate program run to generate magnetic files.
Note that of all three type of magnetic files will be generated together in the same program run. Files with no contents will not be generated, however.
,,REAL MODE AND TEST MODE OF EXECUTION
The report can be run in test or real mode. The difference in functionality between the two modes is that, in real mode, databases are updated and magnetic files can be generated. In test mode, databases are not updated and magnetic files will never be generated.
,,GENERATION OF TEMSE FILE
The user can choose to save results of the program into a TemSe. Saving results to TemSe is not mandatory, except when the program is run in background processing.
,,MISSING MASTER DATA RECORDS AND CREATION OF ACTION RECORDS
When infotype 0369 master data record, which was once processed and sent to ISSSTE as a hiring event, is modified in such a way that the original hiring master data record was deleted and, possibly, a new hiring master data record is created. To compensate for the deletion of a hiring master data record, under certain circumstances, a termination record will be created for the termination magnetic file.
Under the following circumstances, a termination record will be created:
1.,,when the original hiring master data record is deleted, no new infotype record of type hiring was created to replace it.
2.,,when the original hiring master date record is deleted, a new infotype record of type hiring is created with start date later than the start date of the original hiring record.
If a termination record is created, it will have the start date of the original hiring record and last changed date of the record in infotype 0369 that now replaces it.
Note that the same process is followed for the infotype 0369 master data record which was once processed and sent to ISSSTE as a termination event as well, but with a hiring record generated for the hiring magnetic file.
Because of possible creation of these compensating hiring and termination records, not all hiring in the magnetic files come from processing of master data for hiring action type but can also come from the processing of missing termination master data record as well.
In effect, even when there is no hiring record originated from master data to be reported to ISSSTE but a hiring record might can still be generated for hiring magnetic file because of the absence of termination master data record. Same comment is also applied to termination action type.
,,RENOTIFICATION
Renotification allows users to process again action events that have once been included in the magnetic file. The records created from renotification will be included in the same magnetic file as those being created for the first time when the report is run.
In the action list output screen of the report HMXUACTPBS, the user can get renotification information for each entry on the screen from screen column 'RESEND STATUS'.
,,RENOTIFICATION AND CORRECTION OF PAST BASIC QUOTATION WAGE
The user can always choose whether to renotify previously sent records again, except in the case in which a past basic quotation wage is being corrected. When a new change in pay action record is created in an attempt to correct past basic quotation wage, all previously sent change in pay records with start date after the corrected record will always be included in the results.
,,BACK TO BACK HIRING AND BACK TO BACK TERMINATION
If there is more than one hiring action records in a row from one infotype, only the first record is retained in the magnetic file. The same rule is also applied to the termination action records.
,,ISSSTE NUMBER
ISSSTE number in the magnetic file gets its value from the most current infotype 0369 of the employee within time selection period. However, in the event that the employee has infotype 0369 obligation status of 'Exempt from ISSSTE contribution obligation', the value is then read from the previous infotype 0369 record. In the event that ISSSTE number does not exist in the infotype 0369 it is read from due to obligation status of the record being 'subject to contribution obligation without registration number', a warning message is given.
,,BEGIN DATE OF CHANGE IN PAY EVENTS
Change in pay events originated from change in basic quotation wage from changes in infotype 0008, 0014 and 0015 of the employee. The start date of the change in pay action record depends on which infotype causes the change in basic quotation wage.
For infotype 0008 and 0014, the start date of the record causing the change will be used as the start date of the change in pay action record. For infotype 0015, whichever the payroll period the date of origin of infotype 0015 record falls into, the start date of that payroll period will be used as the start date of the change in pay action record. Further more, for infotype 0015, the start date of the next payroll period will be considered as possibly having a change in basic quotation wage as well.
For example, if infotype 0008 record has a new record with start date 10.1.2003 with a value of wage type amount different from the previous record, a change in pay action record will be created with start date of 10.1.2003. If infotype 0014 has a new record with start date of 12.1.2003, a new change in pay action record will be created with start date of 12.1.2003. If infotype 0015 has a new record with date of origin of 20.1.2003, two new change in pay records will be created with start date of 16.1.2003 and 1.2.2003.
For the example described, we assume that the new infotype record causes change in basic quotation wage. If the new record does not cause basic quotation wage to change, there will be no change in pay action records created for the magnetic file.
,,DELETION OF HIRING ACTION INFOTYPE 0000 RECORD
If a hiring record from infotype 0000 Actions has been once sent to ISSSTE and later was deleted from master data of the employee and replaced by a termination record, a termination action record will be generated for the termination action file. However, if the original hiring record had not been sent before it was deleted, then no termination record will be generated for the termination action file.
,,REPORTING OF CHANGE IN PAY AND HIRING
If a change in pay and hiring actions with the same action date are detected in the same program execution, only hiring action will be kept in the result of that program run. For first hiring action, no change in pay will be reported, even in a separate program run.
,,CHANGE IN PAY IN REENTRY INTO THE COMPANY
All change in pay during reentry into the company will be treated as a change in pay actions and will be reported. As reentry will be reported as a hiring action, the behavior of the program that no change in pay and hiring action with the same action date will appear in the same program execution still holds. Hence, change in pay during reentry and the reentry itself will not be reported in the same program run.
,,GENERATING MAGNETIC FILES FROM A TEMSE,,
When the program generated a TemSe file in test mode, relevant databases were not updated. Later, when the user reads the TemSe file which contains the result of the first execution of the report, no magnetic files can be created because proper database updating has not been realized. Hence, reading, with the intention to generate magnetic files, from a TemSe which was originally created in test mode, is not allowed.
,,LIMITATIONS
The program HMXUACTPBS, and its history-uploading program HMXUUAHPBS, have the following limitations.
1.,,Hiring action of an employee must have been reported at least once before any BQW change can be detected correctly by the programs. Reporting both the first hiring and any subsequent BQW changes in the same program run will also be satisfactory.
2.,,Running the program to report a hiring action of an employee, without first properly creating an infotype 0008 Basic Pay for the employee, will result in incorrect detection of subsequent changes in basic quotation wage. Thus, an employee should have infotype 0008 maintained completely before his master data are processed by the programs.
3. If the program is run with field 'Test Mode' unchecked, it is executed in 'real mode' where relevant databases are updated and magnetic files are generated, if the results are error-free. If the program is run with the field checked, then it is executed in 'test mode' where there is no database updating and no magnetic files will be generated. Whichever mode the program is run in, saving the results into a TemSe file is possible but not mandatory, except when the program is run in background mode where saving to a TemSe is mandatory and no magnetic files are generated.
,,
PERFORM Short Reference General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 37158 Date: 20240531 Time: 114155 sap01-206 ( 766 ms )
