×

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




Sapass

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



Index

EEWageComponentExt

EEWageComponentExt


The business object External Employee Salary Element is a
payment or deduction for an employee. The salary element is transferred
to HR by an outside application and is then processed in Payroll. The
salary element to be transferred must be a wage type in the HR format (with amount and characteristics).


Structure


  • Just like the EmployeeAddress and EmployeeBasicpay objects, this object
    is an infotype object that is assigned to the central object type Employee.

  • The object is a specialization of the subtype-dependent object EmployeeInfoSubtype
    . The subtype indentifies the application from which the salary elements originate for the object WAGECOMP.

  • An occurrence in the Business Object Repository (BOR) corresponds to one infotype record.

  • The business object is not country specific.

  • The following methods exist for the business object:

  • Create

  • GetList

  • GetDetail

  • Change

  • Delete

  • 11-Dec-2005


    Methods

    Available Methods


    • Change : Modification of External Wage Component [ BAPI_WAGE_COMP_EXT_CHANGE ]
    • Create : Creation of External Wage Component [ BAPI_WAGE_COMP_EXT_CREATE ]
    • Delete : Deletion of External Wage Component [ BAPI_WAGE_COMP_EXT_DELETE ]
    • GetDetail : Detail Display of External Wage Component [ BAPI_WAGE_COMP_EXT_GET_DETAIL ]
    • GetList : List of Keys for External Wage Components [ BAPI_WAGE_COMP_EXT_GET_LIST ]

    11-Dec-2005


    Change

    Change


    This function module changes an existing record for the External Salary Elements infotype (0579) in HR.

    To determine the key of the record to be changed, use the EEWageComponentExt.GetList BAPI before you use this BAPI.

    This is the only method you can use for changing records for the Salary Elements
    infotype (0579). It is not possible to change them directly in HR.

    The function module runs the following data checks and if the check has a negative result, it returns an error:

  • The personnel number exists in HR.
  • The date on which the salary elements are transferred to Payroll is later than the
    earliest personal retroactive accounting date
    in the Payroll Status infotype (0003) for the employee and is alsolater than the earliest retroactive accounting date in the control record for the employee's payroll area.
  • The account assignment object (account assignment block, posting information) is valid.

  • The HR wage type exists for the employee's country and is permitted for transfer from the application.
  • The employee is actively employed on the validity date of the salary element. If the employee is not active, the run payroll until date is set in the Payroll Status infotype (0003). This means
    that a retroactive run is triggered in the next payroll run. No errors are returned.
  • Example

    Travel Management (TM) triggers a retroactive run in the TM system.This creates a new result that should replace the old result in HR.

    Notes


    Database update

    The BAPI does not execute a Commit Work operation. .This avoidsdatabase updates for each created record. You can control database updates using the BapiService.TransactionCommit or theBapiService.TransactionRollback</ methods. We recommend several BAPI calls (20 to 100) before you use a Commit operation.

    The personnel number is locked from the point when the BAPI is calledto the point when infotypes 0579 and 0003 are updated. The number ofpersonnel numbers processed between two commits should be chosen accordingly:

  • If the personnel number lock is critical, you should use a commit more frequently.

  • If the performance is critical, you should process as many personnel numbers as possible between two commits.
  • Locked personnel numbers

  • Personnel numbers are rejected if they are locked at the time of thetransfer. This is the case, for example, if master data is edited for a personnel number.

  • Payroll status

  • If the payroll area for a personnel number has the status Released for Payroll, you cannot make any changes to the infotype records for this personnel number for the current and past payroll periods. Thepersonnel number is then not rejected but it is stored in matchcode W so that it can be processed in the correction run for Payroll.
  • Retroactive changes

    If salary elements are transferred and they were due in a period for which payroll has already been run, the earliest master data change is set in the Payroll Status infotype (0003) so that a retroactive run is triggered.



    11-Dec-2005


    Create

    Create


    This function module creates a new record for the External Salary Elements infotype (0579).

    With this BAPI, you transfer your salary elements to HR. The HR systemthen saves the elements as an infotype record and they are processed further in Payroll.


    This is the only method available for creating records for the Salary Elements infotype (0579). You cannot create the records directly in HR.

    To ensure that all tests for the creation of a new infotype record are run, you can use the BAPI in a test run. The Test run
    parameter is flagged as a default value.

    The function module runs the following data checks and if the check has a negative result, it returns an error:

  • The personnel number exists in HR.
  • The date on which the salary elements are transferred to Payroll is later than the
    earliest personal retroactiveo accounting date
    in the Payroll Status infotype (0003) for the employee and is alsolater than the earliest retroactive accounting date in the control record for the employee's payroll area.
  • The account assignment object (account assignment block, posting information) is valid.

  • The HR wage type exists for the employee's country and is permitted for transfer from the application.
  • The employee is actively employed on the validity date for the salary element. If the employee is not active, the run payroll to date is set in the Payroll Status infotype (0003). This means that a
    retroactive run is triggered with the next payroll run. No errors are returned.
  • Notes

    Database update

    The BAPI does not execute a Commit Work operation. This avoidsdatabase updates for each created record. You can control database updates using the BapiService.TransactionCommit and
    BapiService.TransactionRollback methods. We recommend that you use several BAPI calls (20 to 100) before you set a Commit operation

    The personnel number is locked from the point when the BAPI is calledto the point when infotypes 0579 and 0003 are updated. The number of
    personnel numbers processed between two Commits should be chosen accordingly:

  • If the personnel number lock is critical, you should set a Commit more frequently.
  • If the performance is critical, you should process as many personnel numbers as possible between two Commits.

  • Locked personnel numbers

  • Personnel numbers are rejected if they are locked at the time of thetransfer. This is the case if, for example, master is edited for a personnel number.
  • Payroll status

  • If the payroll area for a personnel number has the status Released for Payroll
    , you cannot make any changes to the infotype records for this personnel number for the current and past payroll periods. Thepersonnel number is then not rejected but it is stored in matchcode W so that it can be processed in the correction run for Payroll.
  • Retroactive changes

    If salary elements are transferred and they were due in a period for which payroll has already been run, the earliest master data change date is set in the Payroll Status infotype (0003) so that a retroactive run is triggered.


    11-Dec-2005


    Delete

    Delete


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

    Before you use this BAPI, use the EEWageComponentExt.GetList BAPI to determine the key of the record to be deleted.

    This is the only method you can use for deleting transferred records. You cannot delete transferred records in HR.


    The function module runs the following data checks. If the check is negative, it returns an error:

  • The personnel number exists in HR.
  • The date on which the salary elements are transferred to Payroll is later than the earliest personal retroactive accounting date in the Payroll Status infotype (0003) for the employee and is also
    later than the earliest retroactive accounting date in the control record for the employee's payroll area.
  • The account assignment object (account assignment block, posting information) is valid.
  • The HR wage type exists for the employee's country and is permitted for transfer from the application.

  • The employee is actively employed on the validity end date of the salary element. If the employee is not active, the run payroll to date in the Payroll Status infotype (0003) is set. No errors are returned.
  • Notes

    Database update


    The BAPI does not execute a Commit Work operation. This avoidsdatabase updates for each created record. You can control database updates using the BapiService.TransactionCommit orBapiService.TransactionRollback methods. We recommend several BAPI calls (20 to 100) before you set a Commit.


    The personnel number is locked from the point when the BAPI is calledto the point when infotypes 0579 and 0003 are updated. The number ofpersonnel numbers processed between two Commits should be chosen accordingly:

  • If the personnel number lock is critical, you should set a Commit more frequently.

  • If the performance is critical, you should process as many personnel numbers as possible between two Commits.
  • Locked personnel numbers

  • Personnel numbers are rejected if they are locked at the time of thetransfer. This is the case if, for example, master data is edited for a personnel number.

  • Payroll status

  • If the payroll area for a personnel number has the status Released for Payroll, you cannot make any changes to the infotype records for this personnel number for the current and past payroll periods. Thepersonnel number is then not rejected but it is stored in matchcode W so that it can be processed in the correction run for Payroll.
  • Retroactive changes

    If salary elements are transferred and they were due in a period for which payroll has already been run, the earliest master data change date is set in the Payroll Status infotype (0003) so that a retroactive run is triggered.


    11-Dec-2005


    GetDetail

    GetDetail


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

    Before you call this BAPI, use the EEWageComponentExt.GetList BAPI to determine the key of the record to be displayed.

    Use this BAPI to query the status of the transferred data in HR. You
    can display whether external wage components have the status Transferred to infotype or Accounted.

    Example

    You can display the transferred data, or check whether the infotype record has been processed in Payroll yet.



    11-Dec-2005


    GetList

    GetList


    This function module reads all instances of the EEWageComponentExt class that meet the specified selection criteria and returns a table containing HR-internal infotype keys.

    The BAPI enables the external application's keys to be assigned to the HR-internal infotype keys.


    You must call this BAPI before you call the following BAPIs:

  • EEWageComponentExt.Delete
  • EEWageComponentExt.Change
  • EEWageComponentExt.GetDetail
  • The get_list BAPI receives the key of the external application and
    returns the internal infotype key from HR. The HR-internal infotypekeys can then be used to manipulate the corresponding data records using the BAPIs executed above.


    11-Dec-2005