Hierarchy

⤷

⤷

IMG Activity
ID | /ISDFPS/CUST_RELAT | BAdI: Customer-Specific Relationships |
Transaction Code | /ISDFPS/54000076 | (empty) |
Created on | 20040330 | |
Customizing Attributes | /ISDFPS/CUST_RELAT | BAdI: Customer-Specific Relationships |
Customizing Activity | /ISDFPS/CUST_RELAT | BAdI: Customer-Specific Relationships |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /ISDFPS/CUST_RELAT |
Use
This interface is used to create and test customer-specific relationships or those customized by the customer.
For the technical document on the BadI, see the interface documentation of BadI interface /ISDFPS/IF_EX_CUST_RELAT
.
Requirements
Standard settings
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
One application example is the introduction of a new usage type with its own structure based on a customer-specific relationship (for example, for the organization of work). Here, it is necessary first to determine the validity of each object in the F4 help as a relationship parent/child, then to test the entry in the relevant fields, and finally to create the relationships themselves.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
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 | /ISDFPS/CUST_RELAT | 0 | /ISDFPS/KL10000014 | Command and Support Relationships |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20040330 |
SAP Release Created in | 470 |