Hierarchy
⤷ EHS (Application Component) Environment, Health and Safety
⤷ /TDAG/CP_IMDS (Package) IMDS Advanced Interface Integration
IMG Activity
ID | /TDAG/CP_IMDS_BADI_7 | BAdI: Customer Request Processing |
Transaction Code | /TDAG/13000068 | (empty) |
Created on | 20101115 | |
Customizing Attributes | /TDAG/CP_IMDS_BADI_7 | BAdI: Customer Request Processing |
Customizing Activity | /TDAG/CP_IMDS_BADI_7 | BAdI: Customer Request Processing |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /TDAG/CP_IMDS_BADI_7 |
Use
This Business Add-In (BAdI) is used in SAP Product and REACH Compliance. This BAdI enables you to adapt the way that requests are processed in the customer MDS center. This BAdI is called when a customer request is to be rejected or when a material data sheet (MDS) is to be assigned to a customer request.
Requirements
Standard settings
In the standard system, the Business Add-In is activated. The default code is executed automatically. If you activate your own implementation, the default code is deactivated automatically. The BAdI is not filter-dependent.
BAdI Implementations
/TDAG/CL_DEF_IM_CP_IMDS_BADI_7 (default implementation)
A default implementation is supplied for the REJECT_REQUEST and DETERM_REQUEST_ASSIGN methods.
The following methods are provided:
Method Use
REJECT_REQUEST Rejects a customer request
DETERM_REQUEST_ASSIGN Determines the assignment of an MDS to a customer request
These methods comprise only the upload via IMDS Advanced Interface not the download of the result file.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
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 | /TDAG/CP_IMDS_BADI_7 | 0 | HLA0100681 | Product Safety |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | ANDREE | 20101223 |
SAP Release Created in | 200_600 |