Hierarchy
⤷ PY-JP (Application Component) Japan
⤷ P22C (Package) HR customizing: Japan
IMG Activity
ID | OHAJTX230 | BAdI: Maintain Payment Data (FD) Editing Module |
Transaction Code | S_L6B_69000686 | (empty) |
Created on | 20030917 | |
Customizing Attributes | OHAJTX230 | BAdI: Maintain Payment Data (FD) Editing Module |
Customizing Activity | OHAJTX230 | BAdI: Maintain Payment Data (FD) Editing Module |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHAJTX230 |
Business Add-In (BAdI) Change data file content of tax statement by DME (municipal) (PAYJP_EAD_MUNIC_FD ) is called from the report Withholding Tax Statement (RPCEADJ0) when payment report to municipal office is to be submitted via data media (FD). With this Business Add-In, you can edit or change the data record collected by the standard function before creating the final data file to meet customer specific and/or municipal office specific requirements.
The BAdI contains the method SET_ADDITIONAL_FIELDS and CHANGE_DATA_FILE_CONTENTS which are used to change or edit data records. Municipal city code set in a data record is used as a filter value (parameter FLT_VAL) to differentiate editing methods for different municipal offices.
Example
You can use the existing implementations as examples of sample coding for your own implementations (such as PAYJP_EAD_nnnn).
Requirements
You have set up necessary customizing settings to submit payment report to municipal office via data media (FD).
Standard settings
Recommendation
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Further notes
For more information, refer to the BAdI interface and method documentation:
Method: Set additional fields of tax statement by DME (municipal)
Method: Change data file content of tax statement by DME (municipal)
For more information on using Business Add-Ins, refer to the SAP Library under Basis Components ->ABAP Workbench (BC-DWB) ->Changing the SAP Standard (BC)->Business Add-Ins.
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 |
Customizing Attributes | Country Key | Country Name |
---|---|---|
OHAJTX230 | JP | Japan |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHAJTX230 | 0 | HLA0100529 | Evaluations/Statistics |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030917 |
SAP Release Created in | 470 |