Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
LO-WTY (Application Component) Warranty Claim Processing⤷
ISAUTO_WTY (Package) Warranty Processing
IMG Activity
| ID | WTY_CREATE_COPY | BAdI: Data Change After Copying / Creating / Changing |
| Transaction Code | S_KA5_12001178 | (empty) |
| Created on | 20020828 | |
| Customizing Attributes | WTY_CREATE_COPY | BAdI: Data Change After Copying / Creating / Changing |
| Customizing Activity | WTY_CREATE_COPY | BAdI: Data Change After Copying / Creating / Changing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | WTY_CREATE_COPY |
Use
This business add-in (BAdI) is used in the component Warranty Claim Processing.
With this BAdI you can read additional data when creating and changing warranty claims and when copying claim versions, determine default values, enter customer-specific fields, change standard fields, validate fields, and so on.
The BAdI methods are processed both in the editing of a warranty claim via WIN UI and when creating/changing via BAPI (BAPI_WARRANTYCLAIM_CHANGE),IDoc und WEB UI after processing of the standard coding and before price determination and update of the data buffer.
Note When a warranty claim is read from the database and when the object in the claim is changed, the BAdI WTY_READ_SUPPL_DATA is called.
The BAdI has the following methods:
- DATA_CHANGE_COPY
When copying versions determine default values and changes data in the version and item.
Example: After copying the version from the claimant in the version for the reimburser, you want to determine the reimburser according to predefined criteria.
The method is called after the new data has been created and before prices are copied and the data buffer has been updated.
- DATA_CHANGE_CREATE
When creating warranty claims, change data, as long as data already exists.
The method is run whilst the warranty claim is created and if the claim structure has been created, but the data buffer has not been changed for the first time. This is the case both for creating claims via the UI and for creation via IDoc or BAPI.
If you create a claim via the UI, the method is called once for header and version data for the first version. Item data is not yet available. The creation of the first item counts as a change to the claim..
If you create a claim via BAPI, several versions including items can be created. The method is then called for each version before the items are created. Then the method is called again for each version and the items belonging to it.
Note when implementing the method that processing steps are not execute unnecessarily because of multiple method calls.
- DATA_CHANGE_CHANGE
Change data when changing warranty claim data.
This method is called after the first change to the data buffer each time the user has made a change or if the BAPI for changing claim data is called (before the data buffer is updated). The data before the change, as well as the changed data is transferred to the interface.
Requirements
Standard settings
In the default implementation the default values are determined for the creation of a claim or a version from the Customizing for claim type. Furthermore the text for the catalog entries is read, for example, when data is changed so that it can be displayed for the user on the screen.
Activities
Procedure for BAdI Implementation
Example
You can for example preassign the sales organization or the price date (Default: Reference date) with another value.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | WTY_CREATE_COPY | 0 | ALN0000451 | Warranty Claim Processing |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20030131 |
| SAP Release Created in | 471 |
