SAP ABAP IMG Activity /MRSS/SGU_DESC_DETER (BAdI: Determine Description and Quick Info for Assignments)
Hierarchy
☛ MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net
   ⤷ PM-WOC-MO (Application Component) Maintenance Orders
     ⤷ /MRSS/SGU (Package) User Interface for Interactive Planning Board
IMG Activity
ID /MRSS/SGU_DESC_DETER BAdI: Determine Description and Quick Info for Assignments  
Transaction Code /MRSS/58000038   (empty) 
Created on 20050819    
Customizing Attributes /MRSS/SGU_DESC_DETER   BAdI: Determine Description and Quick Info for Assignments 
Customizing Activity /MRSS/SGU_DESC_DETER   BAdI: Determine Description and Quick Info for Assignments 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /MRSS/SGU_DESC_DETER    

Use

You use this BAdI to define new descriptions for the following objects: assignments, time allocations, resources, and totals bars.

Standard settings

The following methods exist:

  • GET_ASSIGNMENT_DESCRIPTION

You use this method to change the description and the quick info of an assignment.

  • GET_TIMESPEC_DESCRIPTION

You use this method to change the description and the quick info of a time allocation.

  • GET_RESOURCE_DESCRIPTION

You use this method to change the description and the quick info of a resource.

  • GET_SUMBAR_DESCRIPTION

You use this method to change the description and the quick info of the totals bars. For the totals bars, the "SUMBAR" standard text is implemented.

The remaining duration of totals bar can also be influenced with the exporting parameter ET_DURATION. This is ideal, for example, when the remaining duration of the totals bar should be shown depending on the confirmed assignment execution.

A prerequisite here is that each capacitive assignment must be represented with its own totals bar. For more information, see also the /MRSS/C_SUMBAR customizing table.

  • GET_TRAVEL_DESCRIPTION

You use this method to determine the description of arrivals and departures for an assignment.

For these five methods, the changing parameters CV_TEXT (description) and CV_TOOLTIP (quick info) are transferred.

  • INIT_ASSIGNMENT_DESCRIPTION

With this method, the texts of all assignments read can be initialized together when the planning board is reestablished. If this method has been implemented, the text for the assignment from return table ET_TEXT_TOOLTIP is used when the planning board is set up.

  • INIT_TIMESPEC_DESCRIPTION

With this method, the texts of all time allocations can be initialized together when the planning board is reestablished. If this method has been implemented, the text for the time allocation from return table ET_TEXT_TOOLTIP is used when the planning board is set up.

  • INIT_SUMBAR_DESCRIPTION

With this method, the texts of all totals bars can be initialized together with the planning board is reestablished. If this method has been implemented, the text for the totals bar from return table ET_TEXT_TOOLTIP is used when the planning board is set up.

The remaining duration of a totals bar can also be influenced with the exporting parameter ET_DURATION. See also the example above.

  • INIT_TRAVEL_DESCRIPTION

With this method, the texts of all read travel times can be initialized at once when the planning board is reestablished. If this method is implemented, the text for the travel time is used from return table ET_TRAVEL_TEXT when the planning board is set up.

As a return value for these four methods, a table is expected containing the GUID of an assignment or time allocation in each row, as well as the description and the quick info.

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  9. Choose Activate

    The code you stored in the method will be run when the application program is executed.

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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 /MRSS/SGU_DESC_DETER 0 HLB0009110 Cross-Application Components 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20090903 
SAP Release Created in 195