Hierarchy

⤷

⤷

IMG Activity
ID | FDM_BADI_FIELDSTAT | Implement Customer Enhancement for Controlling Attribute Maint. Properties |
Transaction Code | S_XBI_29000016 | (empty) |
Created on | 20021112 | |
Customizing Attributes | FDM_257NKU | Attribute: Uncritical User Exits (Non-Required) |
Customizing Activity | FDM_BADI_FIELDSTAT | Implement Customer Enhancement for Controlling Attribute Maint. Properties |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FDM_AR_UI_FIELDSTAT |
Use
You can use the Business Add-In FDM_AR_UI_FIELDSTATUS to influence the field status of the dialog when you create dispute cases in AR.
You can use the method MODIFY_FIELDSTATUS to do this.
Requirements
Standard settings
In the standard, the attributes receive the field status that you have defined in Customizing for the dispute case.
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
You have defined the external reference in the dispute case as not modifiable. However, if a dispute case is created from the AR transactions, you want the clerk to enter the external reference. You achieve this by implementing the BAdI.
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20021112 |
SAP Release Created in | 471 |