×

[PR]この広告は3ヶ月以上更新がないため表示されています。
ホームページを更新後24時間以内に表示されなくなります。




Sapass

 Simplify SAP R/3 development with Excel VBA/VB RFC  
Home> Bapi>EmpWageComponentExt



Index

EmpWageComponentExt

EmpWageComponentExt


No description is available


11-Dec-2005


Methods

Available Methods


  • Change : Modification of External Wage Component [ BAPI_WAGECOMPEXT_CHANGE ]
  • Create : Creation of External Wage Component [ BAPI_WAGECOMPEXT_CREATE ]
  • Delete : Deletion of External Wage Component [ BAPI_WAGECOMPEXT_DELETE ]
  • GetDetail : Detail Display of External Wage Component [ BAPI_WAGECOMPEXT_GETDETAIL ]
  • GetList : List of Transfer Keys for External Wage Components [ BAPI_WAGECOMPEXT_GETLIST ]

11-Dec-2005


Change

Change


This function module changes an existing record of the External Wage Components infotype (0579) in HR.

Before you use this BAPI, use the BAPI EEWageComponentExt.GetList to specify the key of the record you want to change.

Records of the External Wage Components infotype (0579) can only
be changed using this method. You cannot change them directly in HR.

The function module checks the following data and returns an error message if the check is negative:

  • Whether the personnel number exists in HR.
  • Whether the date on which the wage components will flow into payroll is later than the
    Earliest Personal Retroactive Accounting
    date in the Payroll Status infotype (0003) for the employee, and islater than the Earliest Retroactive Accounting date in the control record for the employee's payroll area.
  • Whether the account assignment object (account assignment block, posting information) is valid.

  • Whether the HR wage type exists for the employee's country and is allowed for transfer out of the application.
  • Whether the employee is active on the validity date of the wage component. If he or she is not active, the system sets the Payroll to be run by date in the Payroll Status infotype (0003). This
    triggers retroactive accounting in the next payroll run. No error is returned.
  • Example

    In Travel Management (TM), retroactive accounting is triggered.This can lead to a new result, which replaces the old result in HR.

    Notes


    Database Update

    The BAPI does not execute any Commit Work, which means that thedatabase does not get updated each time a record is created. You can control database updates with the BapiService.TransactionCommit or BapiService.TransactionRollback method. We recommend you make
    a number of BAPI calls (20-100) before you set a commit.

    From the BAPI call to the updating of infotypes 0579 and 0003, thepersonnel number is locked. You should choose the number of personnel numbers to be processed between two commits accordingly:


  • If the locking of the personnel numbers is critical, you should set commits more often.
  • If performance is critical, you should process as many personnel numbers as possible between two commits.
  • Locked Personnel Numbers

  • The system rejects personnel numbers that are already locked at the
    time of the transfer. This is the case, for example, when master data is being edited for a personnel number
  • Payroll Status

  • If the payroll area of a personnel number has the status Released for Payroll, it is not possible to change infotype records for that personnel number for the current or past payroll periods. However, the
    system does not reject the personnel number, but is put in matchcode W, so that it is processed in the payroll correction run.
  • Retroactive Changes

    If wage components are transfered that fall in a period for which payroll has already been run, the system sets the
    Earliest Master Data Change
    date in the Payroll Status infotype (0003), to trigger retroactive accounting.


    11-Dec-2005


    Create

    Create


    This function module creates a new record of the External Wage Components infotype (0579).

    With this BAPI, you transfer HR wage components, which are stored as infotype records in HR and processed further in Payroll.

    Records of the External Wage Components infotype (0579) can only
    be created using this method. It is not possible to create them directly in HR.

    To run all tests for creating a new infotype record, you can use this BAPI in a test run. The Test run parameter is set as a default value.

    The function module checks the following data and returns an error message if the check is negative:


  • Whether the personnel number exists in HR.
  • Whether the date on which the wage components will flow into payroll is later than the Earliest Personal Retroactive Accounting date in the Payroll Status infotype (0003) for the employee, and is
    later than the Earliest Retroactive Accounting date in the control record for the employee's payroll area.
  • Whether the account assignment object (account assignment block, posting information) is valid.
  • Whether the HR wage type exists for the employee's country and is allowed for transfer out of the application.

  • Whether the employee is active on the validity date of the wage component. If he or she is not active, the system sets the Payroll to be run by date in the Payroll Status infotype (0003). Thistriggers retroactive accounting in the next payroll run. No error is returned.

  • Notes

    Database Update

    The BAPI does not execute any Commit Work, which means that thedatabase does not get updated each time a record is created. You can control database updates with the BapiService.TransactionCommit or BapiService.TransactionRollback method. We recommend you make
    a number of BAPI calls (20-100) before you set a commit.

    From the BAPI call to the updating of infotypes 0579 and 0003, thepersonnel number is locked. You should choose the number of personnel numbers to be processed between two commits accordingly:


  • If the locking of the personnel numbers is critical, you should set commits more often.
  • If performance is critical, you should process as many personnel numbers as possible between two commits.
  • Locked Personnel Numbers

  • The system rejects personnel numbers that are already locked at the
    time of the transfer. This is the case, for example, when master data is being edited for a personnel number
  • Payroll Status

  • If the payroll area of a personnel number has the status Released for Payroll, it is not possible to change infotype records for that personnel number for the current or past payroll periods. However, the
    system does not reject the personnel number, but is put in matchcode W, so that it is processed in the payroll correction run.
  • Retroactive Changes

    If wage components are transfered that fall in a period for which payroll has already been run, the system sets the
    Earliest Master Data Change
    date in the Payroll Status infotype (0003), to trigger retroactive accounting.


    11-Dec-2005


    Delete

    Delete


    This function module deletes an existing record of the External Wage Components infotype (0579) in HR.

    Before you use this BAPI, use the BAPI EEWageComponentExt.GetList to specify the key of the record you want to delete.

    Records of the External Wage Components infotype (0579) can only
    be changed using this method. You cannot change them directly in HR.

    The function module checks the following data and returns an error message if the check is negative:

  • Whether the personnel number exists in HR.
  • Whether the date on which the wage components will flow into payroll is later than the
    Earliest Personal Retroactive Accounting
    date in the Payroll Status infotype (0003) for the employee, and islater than the Earliest Retroactive Accounting date in the control record for the employee's payroll area.
  • Whether the account assignment object (account assignment block, posting information) is valid.

  • Whether the HR wage type exists for the employee's country and is allowed for transfer out of the application.
  • Whether the employee is active on the validity date of the wage component. If he or she is not active, the system sets the Payroll to be run by date in the Payroll Status infotype (0003). This
    triggers retroactive accounting in the next payroll run. No error is returned.
  • Notes

    Database Update

    The BAPI does not execute any Commit Work, which means that thedatabase does not get updated each time a record is created. You can control database updates with the
    BapiService.TransactionCommit
    or BapiService.TransactionRollback method. We recommend you makea number of BAPI calls (20-100) before you set a commit.

    From the BAPI call to the updating of infotypes 0579 and 0003, thepersonnel number is locked. You should choose the number of personnel numbers to be processed between two commits accordingly:


  • If the locking of the personnel numbers is critical, you should set commits more often.
  • If performance is critical, you should process as many personnel numbers as possible between two commits.
  • Locked Personnel Numbers

  • The system rejects personnel numbers that are already locked at the
    time of the transfer. This is the case, for example, when master data is being edited for a personnel number
  • Payroll Status

  • If the payroll area of a personnel number has the status Released for Payroll, it is not possible to change infotype records for that personnel number for the current or past payroll periods. However, the
    system does not reject the personnel number, but is put in matchcode W, so that it is processed in the payroll correction run.
  • Retroactive Changes

    If wage components are transfered that fall in a period for which payroll has already been run, the system sets the
    Earliest Master Data Change
    date in the Payroll Status infotype (0003), to trigger retroactive accounting.


    11-Dec-2005


    GetDetail

    GetDetail


    Reads the content of an infotype record and returns the information stored in the infotype.

    Before you use this BAPI, use the BAPI EEWageComponentExt.GetList to specify the key of the record you want to display.

    Use this BAPI to determine the status of the data transfered to HR. The
    system displays whether external wage components have the status

    Transfered to infotype or Settled.

    Example

    You can display the transfered data and see whether the infotype record has already been processed in Payroll.



    11-Dec-2005


    GetList

    GetList


    The EmpWageComponentExt.GetList method enables you to use the availableselection conditions to select specific external wage components. By executing this method, you receive a list of transfer keys forindividual infotype records. You need these keys so that you can edit the corresponding data records using the following methods:

  • EmpWageComponentExt.GetDetail
  • EmpWageComponentExt.Change
  • EmpWageComponentExt.Delete
  • You can select external wage components in different ways:

  • Simple selection:
  • If you only want to make a few restrictions or if you only want to
    specify simple conditions, you can enter data in individual parametersor in a combination of parameters. Use parameters EMPLOYEENUMBER, REFERENCENUMBER, FROMDATE, and TODATE.

  • Complex selection:
  • To effect more complex selections, you can enter data in table
    SELECTCRITERIALIST. You can enter further conditions or make a numberof selections that are independent of each other. To do so, you createa line for each selection and then specify the selection in more detail by entering data in different parameters.


    If you enter data in several parameters for a line, the selectionconditions are linked by AND logic. Other relationships are notpossible; you must subsequently edit the results list that is output.

    The individual lines of SELECTCRITERIALIST each trigger an independent
    selection, that is, they are not linked to each other by AND logic.

  • Combination:
  • You can simultaneously enter data in the individual and fieldsunder SELECTCRITERIALIST. All data in the individual conditions is thenappended as a line to the list of conditions in SELECTCRITERIALIST and
    then edited independently of other selections. For simplicity's sake, you are advised not to combine both selection options.

    An external wage component does not appear more than once in the outputlist, even if it is selected several times by different selections.


    A blank line in SELECTCRITERIALIST causes all external wage components to be selected.

    The EMPLOYEENUMBER, REFERENCENUMBER, FROMDATE, and TODATE parameters are also part of SELECTCRITERIALIST.


    11-Dec-2005