Hierarchy

⤷

⤷

IMG Activity
ID | PLM_AUDIT_TEXT_ID | Definition of Text Types for Each Audit Component |
Transaction Code | S_ABA_72000229 | (empty) |
Created on | 20041221 | |
Customizing Attributes | PLM_AUDIT_TEXT_ID | Definition of Text Types for Each Audit Component |
Customizing Activity | PLM_AUDIT_TEXT_ID | Definition of Text Types for Each Audit Component |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PLM_AUDIT_TEXT_ID |
Use
This Business Add-In (BAdI) is used in the Audit Management (CA-AUD) component.
You use this BAdI to set long text processing for the different audit components.
Requirements
The method GET_TEXT_IDS is only relevant outside of a CRM system.
If you are working in a CRM system, you edit the activity Define Text Objects and Text Types in the Implementation Guide (IMG) instead of the method GET_TEXT_IDS. The text types used in audit management are defined using the text object CGPL_TEXT in the CRM standard system.
Standard settings
The following text types are supplied in the standard system:
Text determination procedure/Object types Description
AQN Audit Management: Audit question
AUO Audit Management: Audit
AUP Audit Management: Audit plan
COR Audit Management: Corrective actions
QUE Audit Management: Question
QUN Audit Management: Question lists
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.
Copy the standard implementation and change the text types for each audit component.
Example
To display the sample code, choose Goto --> Sample Code --> Display.
See also:
Method:
Returns the Text IDs for the XML Transfer of Questions
Returns the Text IDs for the XML Transfer of Audit Questions
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 | PLM_AUDIT_TEXT_ID | 0 | AEC0000474 | Audit Management |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050302 |
SAP Release Created in | 700 |