Hierarchy

⤷

⤷

IMG Activity
ID | FOPC_CI_CASE_FLDATTR | BAdI: Properties of Custom Fields for a Case |
Transaction Code | S_SE3_50000239 | (empty) |
Created on | 20050427 | |
Customizing Attributes | FOPC_CI_CASE_PRINT | BAdIs: Customer Fields for the Case |
Customizing Activity | FOPC_CI_CASE_FLDATTR | BAdI: Properties of Custom Fields for a Case |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FOPC_CI_CASE_FLDATTR |
Use
This Business Add-In (BAdI) is used in the Management of Internal Controls (FIN-CGV-MIC) component.
You use this BAdI to specify the field properties of new customer fields that you have created in Case Management to enhance the user interfaces for assessments, tests, issues, and remediation plans. In this way, you can specify, for example, that a field is a required entry field or that it is locked against entry.
The BAdI is called when assessments, tests, issues, or remediation plans are called in the user interface.
Requirements
- The field must be created by you as a new field. You cannot make changes to delivered fields.
- You have created one or more of the following customer include structures and included the field there:
- Assessments: CI_FOPC_CASEAS
- Issues: CI_FOPC_CASEIS
- Remediation plans: CI_FOPC_CASEPL
- Control Effectiveness Test: CI_FOPC_CASETE
- Test Log: CI_FOPC_CASETL
- Management Controls To Be Tested for an Object: CI_FOPC_CASETE
- Management Control Test: CI_FOPC_CASETL
- You have included the field in the user interface. You do this in transaction CRMC_BLUEPRINT_C.
For more information about creating customer fields, see the relevant Implementation Guide on SAP Service Marketplace at http://service.sap.com/soa -> Documentation.
Standard settings
The BAdI is not active in the standard system. It is not filter-dependent and cannot be used more than once.
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
To display sample coding, choose Goto -> Sample Code -> Display.
See also:
Methods
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 |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050510 |
SAP Release Created in | 600 |