Hierarchy

⤷

⤷

IMG Activity
ID | SIMGOHA_EFIGB_005 | Business Add-In for Infotype Tax |
Transaction Code | S_EH1_67000069 | IMG activity: SIMGOHA_EFIGB_005 |
Created on | 20030923 | |
Customizing Attributes | SIMGOHA_EFIGB_005 | Business Add-In for Infotype Tax |
Customizing Activity | SIMGOHA_EFIGB_005 | Business Add-In for Infotype Tax |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMGOHA_EFIGB_005 |
Business Add-In for Infotype Tax Data GB (0065)
Use
You can use this Business Add-In to make your customer-specific e-Filing checks on:
- Incoming form information
- Issuing customer-specific errors or warnings
Furthermore, you can fill (if necessary) customer-defined infotype fields.
Activities
After executing this 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 and choose Create.
The screen for creating BAdI implementations is displayed.
- Enter a short text for the implementation.
- 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 it was created.
- 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 coding for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
- Save and implement your coding.
- Return to the Edit Implementation screen and save your entries.
Note: You can also create an implementation and activate it at a later point in time. In such a case, end the processing stage at this point.
- Choose Activate.
The coding you stored in the method will be run when the application program is executed.
Further BADI Information
For more information on using Business Add-Ins, refer to the SAP Library under: mySAP Technology Components -> SAP Web Application Server -> ABAP Workbench (BC-DWB) -> Changing the SAP Standard (BC) -> Business Add-Ins.
Standard settings
BADI Method CHECK_0065_UPDATE
The BAdI method 'CHECK_0065_UPDATE ' can be used to check each individual update record before an update occurs to the Tax Data GB infotype (0065). The BAdI is called as a final step before the actual update. Therefore, if no error or warning is issued, the SAP System will try to update the proposed record.
The BAdI method can be used to:
- Fill the customer structure CI_0065, which will then be included with the infotype update.
- Check the proposed update and if necessary issue errors or warnings.
Interface
Import parameters
INCOMING_RECORD
The method provides the filled e-Filing update structure HREFI_UPD_STRUC. This structure contains all the relevent fields in relation to the incoming form.
P0065_CURRENT The current infotype record will be provided.
P0065_INCOMING
The proposed new infotype record from the incoming form
Export Parameters
C_FIELDS
Contains the structure of the customer include CI_0065. In the case that customer fields are maintained, fill the C_FIELDS structure and set the indicator for C_FIELDS-CUST_FIELDS.
Exceptions
UPDATE_ERROR
In the case that the module has found an error situation and the record should not be updated, you must raise an update_error. You should then issue an appropriate message with this exception as an error. In the case that no message is issued with the exception, a standard error text will be defaulted that indicates that an error was raised from this BAdI.
UPDATE_WARNING
In the case that the module has found a warning situation and the record can be updated upon verification you can after verification raise an update warning(see template below). You should then issue an appropriate message with the warning. In the case that no message is issued with the warning, a standard warning text will be defaulted that indicates that a warning was raised from this BADI.
Activities
- In the case that customer specific infotype fields have been filled set the indicator for C_FIELDS-CUST_FIELDS.
- Perform the required customer specific checks and issue errors and warnings as required.
- Activate the implementation once it has been created.
EXAMPLE TEMPLATE
METHOD if_ex_hr_efi_upd0065~check_0065_update.
* ...
DATA answer(1).
* If required fill the customer specific fields on the infotype
* 1) Set the field c_field-cust_fields = 'X' if customer fields have
* been used. If c_field-cust_fields is not set the customer fields will
c_fields-cust_fields = 'X'
* 2) Fill the customer fields as required
c_fields-myfield1 = 'XYZ'
c_fields-myfield2 = 'ABC'
* program a customer specific error by raising the update_error
* exception
* Example:
message e025(zrefigb) with 'HR_EFI_UPD0065' raising update_error.
* program a customer specific warning in this way
****
* 1) Call the function module HR_EFI_SHOW_WARNINGS
* Example
CALL FUNCTION 'HR_EFI_SHOW_WARNINGS'
EXPORTING
update_struc = incoming_record
msgid = 'ZREFIGB'
msgno = 041
msgv1 = 'HR_EFI_UP0065'
msgv2 = space
msgv3 = space
msgv4 = space
IMPORTING
answer = answer.
* 2) raise the exception unless return param answer = 'Y'.
IF answer <> 'Y'. "
MESSAGE w041(zrefigb) WITH 'HR_EFI_UPD0065' RAISING update_warning.
ENDIF.
****
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
SIMGOHA_EFIGB_005 | GB | United Kingdom |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMGOHA_EFIGB_005 | 0 | HLA0100292 | Great Britain |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20040623 |
SAP Release Created in | 46C |