The Ultimate guide to

Customer Enhancements relevant to PM & CS(Release 4.6C)

Contents1. 2. 3. 4. Enhancement List .................................................................................................................................. 2 BAPI List .............................................................................................................................................. 5 Enhancements in Detail ........................................................................................................................ 6 BAPIs in Detail .................................................................................................................................. 88

1. Enhancement ListEnhancement IBase IB020001 IBPP0001 Partner Selection ICRP0201 ICRP0202 ICRP0203 ICSV0001 ICSV0002 ICSV0003 ICSV0004 ICSV0005 ICSV0007 ICSV0008 Master Data IBIP IEQM0001 IEQM0002 IEQM0003 IEQM0004 IEQM0005 IEQM0006 IEQM0007 IHCL0001 ILOM0001 ILOM0002 ITOB0001 ITOB0002 ITOB0003 ITOB0004 Measuring Points/Documents IMRC0001 IMRC0002 IMRC0003 Maintenance Plans IPRM0002 IPRM0003 IPRM0004 IPRM0005 Serial Numbers IQSM0001 IQSM0002 IQSM0003 IQSM0004 IQSM0005 IQSM0007 IQSM0008 IDocs IWMI0001 Orders CNEX0013 IWO10001 IWO10002 IWO10004 IWO10005 IWO10006 Description Filter components Filter IBase Components When Generating From PP Data Search Help CS_ORG_02: Authorization Check Search Help CS_ORG_02: Internally-Programmed Selection Search Help CS_ORG_02: Propose Task Display of geographic location data Automatic task determination for service notifications Partner selection Check PM object and display object information Determining reason for rejection - resource-related billing Serial Number Partner Transfer on Goods Issue and Returns Validation of additional partner types IBIP: Trans. IBIP Data Transfer Add. checks for equip. installation at functional locations Additional checks for definition of equipment hierarchies Additional checks before equipment update Object is allowed for contract partner (Order->MaintCont.) Object allowed for SD contract (MaintContract->MaintCont.) Object allowed for SD contract (Maintain maintenance cont.) Check/change manufacturer field in equipment master Create equipment using material template: Classes/chars Additional checks before saving a functional location User exit when checking structure of location numbers PM: Customer include subscreen for technical object master data ITOB: Field changes to copy model PM: Customer Include subscreen for fleet object data PM: Customer Exit fleet identification data: Checks Measurement Point/Measurement Document: Exit before update (after COMMIT WORK) Measurement Point: Menu exit for customer-specific function Measurement Document: Menu exit for customer-specific function Determine planned date info for maintenance plan User field: Maintenance plan Maintenance plan / item: Customer check for time "SAVE" Determine Offset for Performance-Based Strategy Plans Automatic serial number assignment Check when copying object list Serial numbers, user exit for additional data Serial numbers, user exit after exiting the serial screen Serial numbers, user exit in the update Serial numbers, user exit for goods movements Serial number character string check User exits for SM/PM IDOCs Order: Customer enhancement: Default item category component assignment Create a PM sub-order PM maintenance order: Customer check for order release Maintenance order: Customer check for order completion Maintenance order: Customer-specif. determination of profit centre Maintenance order: FCode exclusion through customer enhancement

IWO10007 IWO10008 IWO10009 IWO10010 IWO10011 IWO10012 IWO10015 IWO10016 IWO10017 IWO10018 IWO10020 IWO10021 IWO10022 IWO10023 IWO10024 IWO10025 IWO10026 IWO10027 IWO10029 IWO20001 COOM0001 COZF0001 COZF0002 CY190001 Billing KSDIEX01 General IWOC0001 IWOC0002 IWOC0003 IWOC0004 IMSMCOMM Confirmation CONF0001 CONFPM01 CONFPM02 CONFPM03 CONFPM04 CONFPM05 CATS CATS0001 CATS0002 CATS0003 CATS0004 CATS0005 CATS0006 CATS0007 CATS0008 CATS0009 CATS0010 CATS0011 CATS0012 CATSBW01 Notifications QQMA0001 QQMA0002 QQMA0003 QQMA0004 QQMA0005 QQMA0006

Maintenance order: Customer enhancement - permits in the order Customer enhancement: Determination of tax jurisdiction code PM Order: Customer Check for 'Save' Event Maintenance order: Customer enhancement for determining WBS element Maintenance order: Customer enhancement for component selection Maintenance order: Priority handling on central header Maintenance order: F4 Help for user fields on operation PM Order: Customer enhancement to check operation user fields Determine external order number by customer logic Maintenance order: User fields on order header Maintenance order: Automatically include task list Automatic task list transfer when creating order from notification Determine calendar from user exit Service order: Change header data for advance shipment doc. Service order: Changes to items for advance shipment PM/SM order: Finding responsible cost centre User check on setting status 'Do not perform' User exit: Generate user-defined settlement rule Inclusion of bill of material in PM/SM order PM order: User exit to pass routing to order Customer Functions for Overhead Percentages Change purchase req. for externally processed operation Change purchase req. for externally procured component Capacity Planning: Change order operation Determining expenditures in resource-related billing Create PM/SM notification: Determine reference object PM/SM notification: Check whether status change is allowed PM/SM authorization check of ref. object and planner group Change single-level list editing PM/QM/SM ALV settings MSM communication enhancement Enhancements in order confirmation PM/SM order conf.: Determine customer specific default values PM/SM order confirmation: Customer specific input checks 1 PM/SM order conf.: Customer specific check after op. Selection PM/SM order conf.: Customer specific input check 2 PM/SM order conf.: Customer specific enhancements when saving CATS: Compile worklist CATS: Supplement recorded data CATS: Validate recorded data CATS: Deactivate functions in the user interface CATS: Customer field enhancements CATS: Validate entire time sheet CATS: Subscreen on initial screen CATS: Determine workflow recipients for approval CATS: Customer-Specific Text Fields in Data Entry Section CATS: Customer-Specific Text Fields in Worklist CATS: Customer functions CATS: Subscreen on data entry screen Customer Exit for Transferring Time Sheets > BW QM/PM/SM: User subscreen for notification header QM: Authorization Check for Entry into Notification Transaction QM: "User data" Function in "Goto" Menu QM: "User data" Function in "Goto -> Item Menu QM: Check Validity of Status Change QM: Automatic Task Determination for Quality Notifications

QQMA0007 QQMA0008 QQMA0009 QQMA0010 QQMA0011 QQMA0012 QQMA0013 QQMA0014 QQMA0015 QQMA0016 QQMA0017 QQMA0018 QQMA0019 QQMA0020 QQMA0021 QQMA0022 QQMA0023 QQMA0024 QQMA0025 QQMA0026 QQMA0027 QQMA0028 QQMA0029 Reporting MCI10001 MCR00001 MCR00002 RMCAF000 External Services Mgt INTERFAC SRV_FRM SRVDET SRVEDIT SRVENTRY SRVESI SRVESKN SRVESLL SRVESSR SRVEUSCR SRVKNTTP SRVLIMIT SRVMAIL1 SRVMSTLV SRVPOWEB SRVQUOT SRVREL SRVSEL Under developmentCRM00001

QM: Default Values when Creating a Notification QM/PM/SM: User Subscreen for Additional Data on Notification Item QM: Predefine QM Order Parameters QM/PM/SM: User Subscreen for Additional Data on Cause QM/PM/SM: User Subscreen for Additional Data on Task QM/PM/SM: User Subscreen for Additional Data on Activity QM: Default Values when Creating a Task QM/PM/SM: Checks before saving a notification QM/PM/SM: User-Exit before Call-Up of F4 Help on Catalogs QM/PM/SM: "User data" Function "Goto" > "Task" Menu QM/PM/SM: "User data" Function "Goto" > "Activity" Menu QM/PM/SM: Deadline setting based on entered priority QM/PM/SM: Default Partner when Creating a Notification QM: Determining BOM Usage at BOM explosion QM/PM/SM: Function "User data" in "Goto" menu QM/PM/SM: "User data" function in "Goto -> Causes" menu QM/PM/SM: "User data" function in "Goto -> Item" menu QM/PM/SM Deactivate function codes in CUA menu PM/SM: Default values when adding a notification PM/SM: Auth. check when accessing notification transaction PM/SM: Default values when adding a task QM: Create notification from confirmation of production order QM/PM/SM: Change Notification Type MCI1: PMIS/QMIS updating LIS: Authorization check for standard analyses Standard analyses: Key figure display LIS: Import External Data for Copy Management Interface for data transfer SRV: Formula calculation (obsolete since 4.0A!) User screen on tab strip of service detail screen Service list control (maintenance/display) Unplanned part of entry sheet (obsolete since Rel. 3.1G) Data conversion entry sheet interface Set account assignment in service line Service line checks Set entry sheet header data User screen on entry sheet tabstrip Setting the account assignment category when reading in, if U Limit check Processing of mail before generation of sheet Conversion of data during importing of standard service cat. Purchase order for service entry in Web Service export/import for inquiry/quotations Changes to comm. structure for release of entry sheet Service selection from non-SAP systems

User Exits in Customer Relationship Management

2. BAPI ListBAPI IQS6 BAPI_SERVNOT_ADD_DATA BAPI_SERVNOT_CHANGEUSRSTAT BAPI_SERVNOT_CLOSE BAPI_SERVNOT_CREATE BAPI_SERVNOT_DEL_DATA BAPI_SERVNOT_GET_DETAIL BAPI_SERVNOT_MODIFY_DATA BAPI_SERVNOT_POSTPONE BAPI_SERVNOT_PUTINPROGRESS BAPI_SERVNOT_SAVE IQS7 BAPI_SERVNOT_COMPLETE_TASK BAPI_SERVNOT_RELEASE_TASK BAPI_SERVNOT_SUCCESSFUL_TASK ITOB_BAPI_EQ BAPI_EQUI_CHANGE BAPI_EQUI_CREATE BAPI_EQUI_CREATE_BY_REFERENCE BAPI_EQUI_DISMANTLE BAPI_EQUI_GETDETAIL BAPI_EQUI_GETLIST BAPI_EQUI_INSTALL ITOB_BAPI_FL BAPI_FUNCLOC_CHANGE BAPI_FUNCLOC_CREATE BAPI_FUNCLOC_GETDETAIL BAPI_FUNCLOC_GETLIST BAPI_FUNCLOC_SET_LABEL_SYSTEM IWWO BAPI_SERVNOT_GETCATALOGPROFIL IWWW BAPI_EQMT_CREATE BAPI_EQMT_DETAIL BAPI_EQMT_DISMANTLEFL BAPI_EQMT_DISMANTLEHR BAPI_EQMT_GETCATALOGPROFIL BAPI_EQMT_GETLISTFORCUSTOMER BAPI_EQMT_INSTALLFL BAPI_EQMT_INSTALLHR BAPI_EQMT_MODIFY BAPI_SERVICENOTIFICAT_CREATE BAPI_SERVICENOTIFICAT_GETLIST MLBO BAPI_ENTRYSHEET_CHECK BAPI_ENTRYSHEET_CREATE BAPI_ENTRYSHEET_DELETE BAPI_ENTRYSHEET_GETDETAIL BAPI_ENTRYSHEET_GETLIST BAPI_ENTRYSHEET_GETRELINFO BAPI_ENTRYSHEET_RELEASE BAPI_ENTRYSHEET_RESET_RELEASE Description CS/SM notifications BAPIs Added Items, Causes, Activities, Tasks, Partners of the service notification Change the user status of a service notification Complete service notification Create service notification Delete Items, Causes, Activities, Tasks, Partners of the service notification Get details about a service notification Modify a service notification or associated sub-data Postpone service notification Put in process a service notification Save service notification CS/SM Tasks BAPIs Complete Notification Task Release Notification Task Release Notification Task PM Equipment: BAPIs PM BAPI: Change Equipment PM BAPI: Create Equipment PM BAPI: Create Equipment with Reference Equipment PM BAPI: Install Equipment (Functional Location, Superior Equipment) PM BAPI: Read Equipment

PM BAPI: Install Equipment (Functional Location, Superior Equipment)

BAPIs for Equipment + Service Notifications Create equipment Read details for equipment Dismantle equipment at functional location Dismantle equipment from equipment hierarchy Determine catalog profile for equipment Select customer equipment Install equipment at functional location Install equipment in equipment hierarchy Change equipment Create service notification Select service notifications according to customer or contact person BAPIs for Entry Sheet (BO 2091) Check Service Entry Sheet Create Entry Sheet Delete Entry Sheet Display Detailed Data on Entry Sheet List Entry Sheets Detailed Release Information Relating to Entry Sheet Release Entry Sheet Cancel Release of Entry Sheets

3. Enhancements in DetailIB020001 Filter components Function exits: EXIT_SAPLIBSD_001 Filter components No documentation in English at present.

IBIP IBIP: Trans. IBIP Data Transfer Function exits: EXIT_SAPLIBIP_001 User Exit: Data Transfer Module (IBIP Batch Input) You can use this enhancement to develop your own data transfer. The advantage of the user exit over an internal ABAP is that the following functions are available to you: Error handling Remote function call Test data functions This extension is called up using transactions IBIP, IBI2 and the ABAP RIIBIP00. User exit EXIT_SAPLIBIP_001 USER EXIT 001: EXIT_SAPLIBIP_001 of expansion IBIP. How it works: Fill out internal table BDCDATA[] (for further information see ABAP LXPMZU01). BDCDATA[] is a table with batch input details. It defines which screens and which fields should be filled with which values. The source from which these field are filled is in INT_TAB[]. Note:

The interface is shifted immediately to the standard work fields. The interface data is moved automatically to other work fields.

Logical interface: You need: - tables

INT_TAB[] "Activity" Menu

Function Code "+US5/6" in Menu "Goto/Activities" in Notification Processing Supply Function Codes/ Deactivate Codes: "Goto/Activity"

EXIT_SAPLIQS0_009 You can use this customer enhancement to activate your own function code for the processing and display transactions of the Notifications: Service, Maintenance and Quality notifications. You can use these function codes, for example, to call a customerspecific screen for the activity. The function codes are in the menu under Goto -> Activity or Goto -> Item -> Activity. EXIT_SAPLIQS0_004 You can use this customer enhancement to activate your own function code for the processing or display transactions of the notifications: Service, Maintenance and Quality notifications You can use these codes, for example, to call a customer-specific screen for an activity. The function codes are included in the menu under Goto -> Activity or Goto -> Item -> Activity. Structure Import parameter I_AKTYP: This parameter displays the transaction type, from which the function is called. A Display V Change H Create Return parameter E_FCODE You use these parameters to control whether the data is to be copied or not. 0001-Continue/Close: The system copies data for the current activity and closes the dialog box. 0002-Next activity selected: The system copies data for the current activity and makes it available for the next activity that has been selected. 0003-Cancel: No data is copied Other-Cancel: No data is copied Note: Before exiting the customer enhancement, you must enter the activity record that has been specified (I_VIQMMA) in the return parameter (E_VIQMMA). This is the only way to ensure that the fields you have not changed are correctly transferred back and that inconsistency of data is avoided.

EXIT_SAPLIQS0_009 You use this function module to dynamically determine the function code text for this customer enhancement. In addition, you can deactivate the function codes that are not being used. Structure Import parameter I_TQ80: This parameter displays the application. I_TQ80-QMTYP = 01 Plant Maintenance I_TQ80-QMTYP = 02 Quality Management I_TQ80-QMTYP = 03 Service Management

Return parameter E_US5_INACTIVE - E_U17_INACTIVE You use this parameter to control the activation or deactivation of the function code in the menu. "X" Function code deactivated in the menu " " Function code active in the menu Return parameter E_US5_TEXT - E_U17_TEXT You use this parameter to define the text that forms the name of the function in the menu. If you do not enter texts, the function codes "+US5", "+US6", "+U14", "+U15", "+U16" und "+U17" appear under the text "Customer data for activities". Note: The function code text can only be defined using this function module. Even if you enter a text using the "Edit component function, the system always displays the text that was given in the relevant return parameter in the function module. The creation of the function code text using the "Edit component" function has no effect. Function Code: You can use this function code to call up a customer-specific view for the notification at activity level. The function code is in the menu under Goto -> Activity. Note: You can only freely define the text for the function code using the function module "EXIT_SAPLIQS0_009". If you do not enter your own text in this function module, the text "Customer data for the activity" is displayed. In addition, you can use the function module "EXIT_SAPLIQS0_009" to deactivate the function code.

QQMA0018 QM/PM/SM: Deadline setting based on entered priority Function exits: EXIT_SAPLIQS0_005 Determining Processing Deadlines According to Priority You can use this customer enhancement to retrospectively change the processing deadlines that the system has determined using the Customizing settings for the priority.

QQMA0019 QM/PM/SM: Default Partner when Creating a Notification Function exits: EXIT_SAPLIQS0_006 Default Partner When Adding A Notification You can use this customer enhancement to enter default values for the partner function, when creating one of following notifications: Maintenance notification Quality notification Service notification Time of call: From the initial screen Quality notifications: Program SAPLIQS0, screen 0200; after the initial screen has been called (if one is called) Maintenance and service notifications: Program SAPLIQS0, screen 0100;

QQMA0020 QM: Determining BOM Usage at BOM explosion Function exits: EXIT_SAPLIQS0_007 Determination of BOM application for BOM Explosion You can use this customer enhancement to influence the result of the BOM explosion function on the item detail screen. The following parameters have the following effects: Parameter E_GRAF: Controls the representation Parameter E_LEVDO: Determines the representation depth Parameter E_CAPID: The BOM application stored in this parameter represents a procedure for automatic alternative determination. In the standard system, the entry in table TQSS is copied as the BOM application. A production or process order must be entered in the notification, so that the BOM application is copied according to the Customizing settings for the order type and for the plant.

QQMA0021 Menu entries: SAPLICUA+U01 SAPLICUA+U02 SAPLICUA+U03 SAPLQM00+U01 SAPLQM00+U02 SAPLQM00+U03 SAPMIWO0+U01 SAPMIWO0+U02 SAPMIWO0+U03 Function exits: EXIT_SAPLIQS0_010 EXIT_SAPLIQS0_011

QM/PM/SM: Function "User data" in "Goto" menu

Function Codes in Menu "Goto/Notification" in Notification Processing Supply Function Codes with Text/ Deactivate Codes: "Goto/Notification"

You use this customer enhancement to activate your own function codes for the notification processing and display transactions, that is: Service notifications Maintenance notifications Quality notifications You can use these function codes, for example, to call up a customer-specific view. The function codes are included in the menu under Goto -> Notification Function Module: This user exit allows you to display a subscreen on the item detail screen (SAPLIQS0 3030). You can maintain your own fields for the item on this screen. An area of three lines is reserved in the screen SAPLIQS0 3030. The screen must be of the "subscreen" type. The structures VIQMEL and VIQMFE are available for purposes of displaying your own fields. The transferred structures are saved in the global structures VIQMEL and VIQMFE. Before you leave the user exit, the structure VIQMFE must be transferred back to the export structure E_VIQMFE. As a result, the fields that you have not changed are transferred back completely, and inconsistencies in the database are avoided. On the basis of import parameter I_AKTYP, you can determine the transaction type from which the function is called up: A - Display V - Change H Create EXIT_SAPLIQS0_011 You can use this customer enhancement to activate your own function code for the processing or display transactions of the quality notifications. You can use these function codes, for example, to call a customer-specific view. The function codes are included in the menu Goto -> Notification Structure Import parameter I_AKTYP: This parameter displays the transaction type, from which the function is called. A Display V Change H Create

Return parameter E_FCODE You use these parameters to control whether the data is to be copied or not. 0001-Continue/Close: Data is copied 0002-Cancel: No data is copied Other-Cancel: No data is copied

Note: Before exiting the customer enhancement, you must enter the notification record that has been specified (I_VIQMEL) in the return parameter (E_VIQMEL). This is the only way to ensure that the fields you have not changed are correctly transferred back and that inconsistency of data is avoided. EXIT_SAPLIQS0_011 You use this function module to dynamically determine the function code text for this customer enhancement. In addition, you can deactivate the function codes that are not being used. Structure Import parameter I_AKTYP: This parameter displays the transaction type from which the function is called. A Display V Change H Create Import parameter I_TQ80: This parameter displays the application. I_TQ80-QMTYP = 01 Plant Maintenance I_TQ80-QMTYP = 02 Quality Management I_TQ80-QMTYP = 03 Service Management Return parameter E_U01_INACTIVE - E_U03_INACTIVE: You use this parameter to control the activation or deactivation of the function code in the menu. "X" Function code deactivated in the menu " " Function code active in the menu Return parameter E_U01_TEXT - E_U03_TEXT: You use this parameter to define the text that forms the name of the function in the menu. If you do not enter texts, the function codes "+U01", "+U02" and "+U03" appear under the text "Customer data for notifications". Note: The function code text can only be defined using this function module. Even if you enter a text using the "Edit component" function, the system always displays the text that was given in the relevant return parameter in the function module. The creation of the function code text using the "Edit component" function has no effect.

Function code: You can use this function code, for example, to call a customer-specific view. The code is in the menu under Goto. Note: You can only freely define the text for the function code using the function module "EXIT_SAPLIQS0_011". If you do not enter your own text in this function module, the text "Customer data for the notification" is displayed. In addition, you can use the function module "EXIT_SAPLIQS0_011" to deactivate the function code.

QQMA0022 QM/PM/SM: "User data" function in "Goto -> Causes" menu Menu entries: SAPLICUA+U18 SAPLICUA+U19 SAPLICUA+U20 SAPLQM00+U18 SAPLQM00+U19 SAPLQM00+U20 SAPMIWO0+U18 SAPMIWO0+U19 SAPMIWO0+U20 Function exits: EXIT_SAPLIQS0_012 Function Codes in "Goto/Cause" Menu in Notification Processing EXIT_SAPLIQS0_013 Supply Function Codes with Text/ Deactivate Codes: "Goto/Cause" You use this customer enhancement to activate your own function codes for the notification processing and display transactions, that is: Service notifications Maintenance notifications Quality notifications You can use these function codes, for example, to call up a customer-specific view for the cause. The function codes are included in the menu under Goto -> Item -> Causes. EXIT_SAPLIQS0_012 You can use this customer enhancement to activate your own function code for the processing or display transactions of the notifications: Service notifications Maintenance notifications Quality notifications You can use these function codes, for example, to call a customer-specific view for a cause. The function codes are in the menu under Goto -> Item -> Cause. Structure Import parameter I_AKTYP: This parameter displays the transaction type from which the function is called. A Display V Change H Create Return parameter E_FCODE: You use this parameter to control whether or not the data is to be copied. 0001-Continue/Close: The system copies data for the current cause and closes the dialog box. 0002-Next task selected: The system copies data for the current cause makes this data available for the next cause that has been selected. 0003-Cancel: No data is copied Other-Cancel: No data is copied Note: Before exiting the customer enhancement, you must enter the cause record that has been specified (I_VIQMUR) in the return parameter (E_VIQMUR). This is the only way to ensure that the fields you have not changed are correctly transferred back and that inconsistency of data is avoided.

EXIT_SAPLIQS0_013 You use this function module to dynamically determine the function code text for this customer enhancement. In addition, you can deactivate the function codes that are not being used. Structure: Import parameter I_TQ80: This parameter displays the application. I_TQ80-QMTYP = 01 Plant Maintenance I_TQ80-QMTYP = 02 Quality Management I_TQ80-QMTYP = 03 Service Management

Return parameter E_U18_INACTIVE - E_U20_INACTIVE: You use this parameter to control the activation or deactivation of the function code in the menu. "X" Function code deactivated in the menu " " Function code active in the menu

Return parameter E_U18_TEXT - E_U20_TEXT: You use this parameter to define the text that forms the name of the function in the menu. If you do not enter texts, the function codes "+U18", "+U19" and "+U20" appear under the text "Customer data for cause" Note: The function code text can only be defined using this function module. Even if you enter a text using the "Edit component function, the system always displays the text that was given in the relevant return parameter in the function module. The creation of the function code text using the "Edit component" function has no effect. Function code: You can use this function code, for example, to call a customer-specific view at cause level in the notification. The function code is in the menu under Goto -> Item -> Causes. Note: You can only freely define the text for the function code using the function module "EXIT_SAPLIQS0_013". If you do not enter your own text in this function module, the text "Customer data for the cause" is displayed. In addition, you can use the function module "EXIT_SAPLIQS0_013" to deactivate the function code.

QQMA0023 QM/PM/SM: "User data" function in "Goto -> Item" menu Menu entries: SAPLICUA+U21 SAPLICUA+U22 SAPLICUA+U23 SAPLQM00+U21 SAPLQM00+U22 SAPLQM00+U23 SAPMIWO0+U21 SAPMIWO0+U22 SAPMIWO0+U23 Function exits: EXIT_SAPLIQS0_014 Function Codes in Menu "Goto/Item" in Notification Processing EXIT_SAPLIQS0_015 Supply Function Codes with Text/Deactivate Codes: "Goto/Item" You use this customer enhancement to activate your own function codes for the notification processing and display transactions, that is: Service notifications Maintenance notifications Quality notifications You can use these function codes, for example, to call up a customer-specific view for the item. The function codes are included in the menu under Goto -> Item EXIT_SAPLIQS0_014 You can use this customer enhancement to activate your own function code for the processing or display transactions of the notifications: Service notifications Maintenance notifications Quality notifications You can use these function codes, for example, to call a customer-specific view for the item. The function codes are in the menu under Goto -> Item. Structure Import parameter I_AKTYP: This parameter displays the transaction type from which the function is called. A Display V Change H Create Return parameter E_FCODE: You use this parameter to control whether or not the data is to be copied.

0001-Continue/Close: The system copies data for the current item and closes the dialog box. 0002-Next item selected: The system copies data for the current item and makes the data available for the next item that has been selected. 0003-Cancel: No data is copied Other-Cancel: No data is copied

Note: Before exiting the customer enhancement, you must enter the item record that has been specified (I_VIQMFE) in the return parameter (E_VIQMFE). This is the only way to ensure that the fields you have not changed are correctly transferred back and that inconsistency of data is avoided. EXIT_SAPLIQS0_015 You use this function module to dynamically determine the function code text for this customer enhancement. In addition, you can deactivate the function codes that are not being used. Structure Import parameter I_TQ80: This parameter displays the application. I_TQ80-QMTYP = 01 Plant Maintenance I_TQ80-QMTYP = 02 Quality Management I_TQ80-QMTYP = 03 Service Management Return parameter E_U21_INACTIVE - E_U23_INACTIVE: You use this parameter to control the activation or deactivation of the function code in the menu. "X" Function code deactivated in the menu " " Function code active in the menu Return parameter E_U21_TEXT - E_U23_TEXT: You use this parameter to define the text that forms the name of the function in the menu. If you do not enter texts, the function codes "+U21", "+U22" and "+U23" appear under the text "Customer data for the item". Note: The function code text can only be defined using this function module. Even if you enter a text using the "Edit component" function, the system always displays the text that was given in the relevant return parameter in the function module. The creation of the function code text using the "Edit component" function has no effect. Function code You can use this function code, for example, to call a customer-specific view at item level in the notification. The function code is in the menu under Goto -> Item. Note: You can only freely define the text for the function code using the function module "EXIT_SAPLIQS0_015". If you do not enter your own text in this function module, the text "Customer data for the item is displayed. In addition, you can use the function module "EXIT_SAPLIQS0_015" to deactivate the function code .

QQMA0024 QM/PM/SM Deactivate function codes in CUA menu Function exits: EXIT_SAPLIQS0_016 Function Module for Deactivating Notification Function Codes You use this customer enhancement to deactivate function codes in the menu for the notification, that is: Service notifications Maintenance notifications Quality notifications Structure Import parameter I_TQ80: This parameter contains the Customizing settings for the current notification type. Import parameter I_AKTYP: This parameter displays the transaction type from which the function is called. A Display V Change H Create Import parameter I_VIQMEL: This parameter contains data for the current notification. Table T_EX_FCODE This table contains all function codes that should not be active during notification processing. You must include the function codes in this table that you want to deactivate using this customer enhancement. When the enhancement is called, this table contains all the function codes that were identified as to be deactivated. Do not delete any of these entries, since inconsistent system statuses can then occur.

QQMA0025 PM/SM: Default values when adding a notification Function exits: EXIT_SAPLIQS0_017 Default Values when Adding PM/CS Notification With this customer exit you can set default values when creating a maintenance notification or service notification. Time of the call: On the initial screen (program SAPLIQS0, screen 0100) when creating a notification in the foreground. After the notification is initialized, if this notification was not created in the foreground. Note: If you want to attach your own fields to the view VIQMEL, you must include it as an APPEND structure in the table QMEL. The additional fields are then copied automatically into the VIQMEL view. Caution: Before you exit the function module for the customer exit, you must enter the transferred notification header record (I_VIQMEL) in the return parameter (E_VIQMEL). This allows the fields that you have not changed to be returned completely and avoids data inconsistency.

QQMA0026 PM/SM: Auth. check when accessing notification transaction Function exits: EXIT_SAPLIBER_001 Customer Exit: Authorization Check for Notification Transactions You can use this customer enhancement to perform an individual authorization check when a quality notification is accessed. This customer enhancement is called up after the SAP standard inspection for authorization object Q_QMEL. The following tables are available in the function exit for user-defined authorization checks: VIQMEL - Notification header record TQ80 - Notification type

QQMA0027 PM/SM: Default values when adding a task Function exits: EXIT_SAPMIWO0_021 Default Values When Creating a Task This customer exit enables you to set default values when adding a task. The customer exit is called in one of the following situations: After you have entered the task After you have executed the function for task determination Notes: Before you leave the function module exit, you must give the transferred task record (I_VIQMSM) to the return parameter (E_VIQMSM). This is the only way to ensure that the fields that you have not changed are returned completely, thus avoiding data inconsistencies.

QQMA0028 QM: Create notification from confirmation of production order Function exits: EXIT_SAPLCORU_S_001 QM: Create Notification from Confirmation of Production Order You can create quality notifications when you make confirmations for a production order. You can use this customer enhancement to load additional information which can be transferred to the quality notification that you want to create.

QQMA0029 QM/PM/SM: Change Notification Type Function exits: EXIT_SAPLIQS0_018 Check Whether a Change of Notification Type is Allowed EXIT_SAPLIQS0_019 No documentation in English at present.

IMSMCOMM MSM communication enhancement Function exits: EXIT_SAPLI_MSM_COMM_001 Determination of Communication Text IMSMCOMM gives you the chance to implement your own way of finding a text that is sent out via the paging functionality from >=45 to a radio device. When you press the paging button in order / notification then (1) we try to find a standard text from customizing (2) substitute the text symbols from (1) like &caufvd-aufnr& by the "real" value (3) send the text from (2) to the user exit (4) present the text from (3) on the paging screen (5) give the text form (4) again to the user exit (there are two events documented) (6) save and send out the text from (5) via sap-connect.

INTERFAC Interface for data transfer Menu entries: RM11RL00+DWN External system RM11RL00+UPL External system Function exits: EXIT_RM11RL00_001 User Exits: Export Data EXIT_RM11RL00_002 User Exit: Adopt Data No documentation in English at present.

MCI10001 MCI1: PMIS/QMIS updating Function exits: EXIT_SAPLMCI1_001 PMIS/QMIS User Exit: Update The user exit EXIT_SAPLMCI1_001 is called while updating data to the PM and QM information systems. The following data is made available: I_CONTROL-VRSIO: Update version I_STAFO : Update group I_ZEITP : Update event I_MCIPMB : Update data for hierarchy 'A' I_MCIQFB : Update data for hierarchy 'B' I_MCINF : Info structures that are updated for the statistical setup. The fields I_MCIPMB-SUPKZ and I_MCIQFB-SUPKZ flag the records in the tables as Before Image" with the value 1 and "After Image" with the value 2. "Before Image" reflects the status of the record in the database and "After Image" reflects the status of the record in the current processing.

MCR00001 LIS: Authorization check for standard analyses Function exits: EXIT_RMCREPAU_001 LIS: Authorization Check for Characteristics (Standard Analyses) Function exit for the authorization check in the LIS standard analyses Before the standard analysis is carried out, an authorization check is made on certain characteristics of an information structure. This check is based on the authorization objects in the standard R/3 system. In addition, you can use the enhancement MCR00001 to perform a user-defined authorization check. The function exit has the following parameters: Import parameters I_MCINF: Info structure designed to identify the respective analysis I_DOMNAME: Domain for the corresponding selection criterion I_ROLLNAME: Data element for the corresponding selection criterion Changing parameter C_END_CHECK: Flag which helps you to control whether the standard authorization check should be carried out via the SAP authorization objects in addition to the authorization check using the enhancement MCR00001. This parameter is only relevant in those cases where the characteristics have a standard authorization object. The parameter has the value ' ' when called up. If you set the parameter to 'X' in the enhancement, there will be no further authorization check in the standard analysis for the current characteristic. Table parameters T_SEL_OPTION: Table with the restrictions for a characteristic. When you call up the enhancement, the table will contain the restrictions that the user specified in the selection screen in the selection criterion for the corresponding characteristic. Example: Selection criterion for plant (name 'SL_0001'). The user wants to select the plants '0001' to '0003' and also plant '0005'. In this case, the table contains the following entries: SELNAME KIND SIGN OPTION HIGH LOW SL_0001 S I BT 0001 0003 SL_0001 S I EQ 0005 These entries in the table allow the authorization check to take place in the enhancement MCR00001. This means that the characteristic values for which the user has no authorization must be attached to the table by filling the field SIGN with the value 'E' (for Exclude). Example: The user does not have any authorization for the plant '0002'. When leaving the enhancement, the table must contain the following: SELNAME KIND SIGN OPTION HIGH LOW SL_0001 S I BT 0001 0003 SL_0001 S I EQ 0005 SL_0001 S E EQ 0002 new line The program will consequently issue the message: "Authorization check: Selection '&3' was restricted". Changes in the procedure The system will no longer automatically perform those authorization checks that could be carried out before Release 3.0C using the report ZMCREAPU. You can now integrate such a check in the enhancement (refer to the sample coding).

MCR00002 Standard analyses: Key figure display Function exits: EXIT_SAPLMCS2_001 Change Key Figure Texts in Standard Analyses SAP enhancement: MCR00002, function exit: EXIT_SAPLMCS2_001 Changing key figure texts in standard analyses Description: This SAP enhancement enables you to do the following in the standard analysis of the Logistics Information System: Define the preset key figures depending on the drill-down level.

Change the text (= column heading) for individual key figures. The standard analysis usually gets the heading for a key figure from the Data Dictionary. (The system reads a text (= field label) which is assigned to the respective data element in the Dictionary). The above SAP enhancement allows you to make your own column headings which differ from data element field labels of the respective key figure. Key figure headings can also consist of two lines. This function exit enables you to create and change the second line of a heading. Display key figure texts that are dependent on the characteristic value, when using the function "All key figures... (display)". Example If you call up this function for material 1, you can, for instance, display the text "quantity of sulphur ordered" instead of the key figure text "order quantity", while in the same place "quantity of chlorine ordered" appears for material 2. The system always calls up the function exit before it displays a list (initial or drill-down list). This means that you can change the preset key figures from list to list. You can therefore configure the key figure view according to the drill-down level. Example At vendor level (= initial list) the key figures A, B and C are displayed. If the user wants to display all materials for a specific vendor (drill down according to material), then he/she can use this function exit to preset the key figures D and E for the drill-down list. The changes made by the function exit remain in effect for all subsequent drill-down lists, i.e. for all subordinate lists in the drill-down hierarchy, until the key figure setting is changed again by the function exit. In the above example, this means that the system will still continue to display the key figures D and E if you drill down on a material according to period and the function exit does not change the key figure setting again before displaying the period list. Input parameters: T_AUS_S000: Contains the data prepared for the screen output of an initial or drill-down list. T_DRILLDOWN: Current drill-down level. In the field T_DRILLDOWN-DDICFELD: the header line of this table contains the name of the characteristic according to which the drill down is performed for the list contained in table T_AUS_S000. (Example: if the field name MATNR is in the DDICFELD, then in the case of the list which is displayed after calling up the function exit, the user is given a material overview.) DDICFELD is a field in the info structure on which the standard analysis is based. Alternatively, you can also request the field T_DRILLDOWN-ROLLNAME in order to determine the current drill-down level. T_DRILLDOWN-ROLLNAME contains the Dictionary data element of the characteristic according to which the drill-down is performed on the list contained in table T_AUS_S000. T_KEY_FIGURES: Preset key figures. MCINF: Name of the info structure that contains the key figures. FLG_ALL_FIGURES: This import parameter contains the value 'X if the function exit is called up before the popup which displays all key figures appears. If an initial or drill-down list is called up then this parameter is reset (i.e. contains a space). OBJECT: Name of the characteristic value (e.g. material or vendor number), for which the user has called up the function "All key figures ... display" (FLG_ALL_FIGURES = X'). Export parameter T_KEY_FIGURES: Key figures preset for the next list. Procedure: Show/hide key figures: You can show and/or hide key figures by either inserting or deleting the line belonging to the key figure in the table T_KEY_FIGURES. If you insert a line in table T_KEY_FIGURES, you only need to fill the fields TABNAME and FIELDNAME. The remaining fields of the tables T_KEY_FIGURES are filled automatically by the standard analysis. TABNAME contains the name of the info structure from which the info structure with the table field name FIELDNAME originates. Change key figure texts (headings): You can find key figure texts in the following four fields of the table T_KEY_FIGURES (the following notation applies to the number of characters permitted): (x) = maximum length [x] = recommended length (in bytes).

SCRTEXT_S = short key word (10) [10] SCRTEXT_M = medium key word (20) [15] SCRTEXT_L = Long key word (40) [20] REPTEXT = program heading (55) [output length of the key figure] When overwriting these four data fields, please observe that the length of the shortest text affects the column width in which the respective key figure is displayed during the standard analysis. This column width is determined as follows: An output length is assigned to each key figure in the ABAP/4 Dictionary. If you select (in the standard analysis via the menu sequence: "Settings -> Column width -> Key figures") a column width that is longer than the output length of a key figure, the system ignores your entry and displays the key figure in its output length. If the shortest key figure text is longer than the output length, then the system uses the length of the shortest key figure text for the column width. If all four key figure texts in the function exit are NOT filled, then the standard analysis fills the empty text fields in accordance with the following logic: If at least one text field has been filled, the standard analysis copies one of these texts into the empty text fields. If no text has been defined in the function exit at all, the standard analysis takes the key figure texts from the Data Dictionary. The field HEADLINE_2 is used to control the second line of the key figure heading. If you require a second line, then you need to fill this field accordingly. Additional information / tips: For certain purposes it might be necessary to access the table T_AUS_S000. For instance, you might want to read the characteristic texts, in order to find out which key figure texts need to be defined. Table T_AUS_S000 is made up of two parts. The first part is independent of the information structure and is therefore always identical. The fields in this part are defined in the structure AUSTAB_GLOBAL (see program RMCS0TP1). The second part of T_AUS_S000 contains the key figure fields. The structure of this part is therefore dependent on the info structure. In order to access the fields in table T_AUS_S000, you therefore need to define a structure in the function exit, which agrees with the structure of table T_AUS_S000. You can find out the structure of this table in the respective main program. You can find out the name of the main program by displaying the status during the standard analysis in question (menu path: System -> Status). To access the data in table T_AUS_S000, you need to ensure that the lines of T_AUS_S000 that you require are read and then moved to the structure defined in the function exit.

RMCAF000 LIS: Import External Data for Copy Management Function exits: EXIT_RMCAF000_001 Read External Data for Data Enhancement User Exit to introduce external data into LIS info structures This Customer Exit is designed to write external data into the info structures of LIS. It can be used, for example, to integrate statistical data from an old system into the LIS. The User Exit is called up in the reorganization tool. For the source info structure, select that info structure, into which you want to write data. Provided that you have activated the User Exit, which provides data for the selected source info structure and you selected the option 'Source data via User Exit', the data collection will be transferred to the User Exit. Input parameters: 1. I_GSTRU: Name of the table for the info structure (e.g., S001, S601) 2. I_INDEX: Index of the first entry of a new packet: Data collection should be carried out in blocks. If you want to process blocks of 500 entries, for example, the variable I_INDEX will supply the value one when the user exit is called up for the first time, and after the first block is updated (and therefore when the user exit is called up for the second time), the I_INDEX will supply the value 501. 3. I_FPATH: path name of the data to be imported (for example, /oracle/C11/data.1993) Table parameters 4. T_DATA: Table with statistics data: Statistical data is read and prepared in the User Exit. This statistical data is processed in the table structure of the info structure (I_GSTRU). This structure is expected in the transfer. 5. I_SELECT_OPTIONS: Table with selection options: Contains the selection options for characteristics and selection-capable key figures that were specified on the selection screen of the report. This allows the data to be selectively read. I_SELECT_OPTIONS has the structure RSPARAMS: SELNAME Name of the selection option from the report. The name of the selection option is found by displaying the F1 Help and carrying out the function 'Technical info'. KIND 'S' for SELECT-OPTIONS SIGN See ABAP/4 Documentation on SELECT-OPTIONS OPTION See ABAP/4 Documentation on SELECT-OPTIONS LOW See ABAP/4 Documentation on SELECT-OPTIONS HIGH See ABAP/4 Documentation on SELECT-OPTIONS Exceptions 6. NO_MORE_DATA: No more exist. The User Exit is again called after the last block of data is read, prepared and processed. RAISE NO_MORE_DATA is a signal by the User-Exit that there are no more data available.

SRVDET Function exits: EXIT_SAPLMLSP_040 EXIT_SAPLMLSP_041 Screen areas: SAPLMLSP0220_SUSCUSER_SAPLXMLU0299 No documentation in English at present.

User screen on tab strip of service detail screen Transfer of Data to Detail User Screen Adoption of Data from User Screen

SRVEDIT Function exits: EXIT_SAPLMLSR_001

Service list control (maintenance/display) User Exit: Control of Service Entry Mode

No documentation in English at present.

SRVESI Data conversion entry sheet interface Function exits: EXIT_SAPLMLSX_002 Conversion/Checking of Entry Sheet Data in Inbox EXIT_SAPLMLSX_003 Conversion of Entry Sheet Data in Outbox The enhancement SRVESI is part of the interface for exchanging entry sheets with external systems (laptop, vendor system). BAPIs are used to both pick out the data needed to create the entry sheets (purchase orders, contracts, service master records) and actually create the entry sheets. In outbound processing, the components of the enhancement are used to convert the data of the BAPIs BAPI_SERVICE_GET_DETAIL and BAPI_PO_GETDETAIL into a document which is then sent by mail or outputted on a data carrier. In inbound processing, the data of the incoming documents is converted to the interface structures of the BAPI BAPI_ENTRYSHEET_CREATE. EXIT_SAPLMLSX_002 The exit EXIT_SAPLMLSX_002 is part of the interface for exchanging entry sheets with external systems (laptop, vendor system). The exit is used to convert the data from incoming documents (mail, file) to the internal data structures. The data of the incoming document is passed on to the exit unchanged. The structures of the BAPI BAPI_ENTRYSHEET_CREATE are expected as output. The exception WRONG_DOCUMENT can be triggered if the data of the inbound document is incorrect.

SRVESKN Set account assignment in service line Function exits: EXIT_SAPLMLSK_001 Set Account Assignment in Service Line The enhancement SRVESKN enables you to predefine the account assignment distribution in newly created service lines. The enhancement is invoked in all purchasing documents with account assignment. Functional module: The function module EXIT_SAPLMLSK_001 allows you to predefine the account assignment distribution in new service lines that are created. Beforehand, you must specify the account assignments and the percentages or quantities allocated to each account assignment in table T_ESKN. The function module is invoked in all purchasing documents with account assignment.

SRVESLL Service line checks Function exits: EXIT_SAPLMLSP_030 User Exit: Fill ESLL Structure Before Checks (After Entry) EXIT_SAPLMLSP_031 Check ESLL Data After Checking No documentation in English at present.

SRVESSR Set entry sheet header data Function exits: EXIT_SAPLMLSR_010 Set Entry Sheet Header Data The enhancement SRVESSR enables you to set the header data (e.g. location at which the service was performed) when creating an entry sheet.

SRVEUSCR Function exits: EXIT_SAPLMLSR_020 EXIT_SAPLMLSR_021 Screen entries: SAPLMLSR0400_SUBUSCR_SAPLXMLU0399 No documentation in English at present.

User screen on entry sheet tabstrip Transfer of Data to Entry Sheet User Screen Adoption of Data from Entry Sheet User Screen

SRVKNTTP Setting the account assignment category when reading in, if U Function exits: EXIT_SAPLMLSX_001 Entry Sheet Upload: Set Account Assignment Category No documentation in English at present.

SRVLIMIT Limit check Function exits: EXIT_SAPLMLSL_001 Check Limits in Service Specifications No documentation in English at present.

SRVMAIL1 Processing of mail before generation of sheet Function exits: EXIT_SAPLMLSX_010 Process Mail Before Generation of Entry Sheet EXIT_SAPLMLSX_011 After Importing Mail, Analysis of Result The enhancement SRVMAIL1 enables you to modify the data of incoming mails (with service entry sheet data). After Release 4.0B, the enhancement SRVESI should be used instead of enhancement SRVMAIL1, since the former offers greater functionality.

SRVMSTLV Conversion of data during importing of standard service cat. Function exits: EXIT_SAPLMLST_001 Conversion of Units of Measure When Importing Standard Service Catalog The enhancement SRVMSTLV facilitates the conversion of data during the importing of standard service specifications.

SRVPOWEB Purchase order for service entry in Web Function exits: EXIT_SAPLMEW5_001 Purchase Order: Entry Sheet Web No documentation in English at present.

SRVQUOT Service export/import for inquiry/quotations Function exits: EXIT_SAPMM06E_010 Export of Service RFQ Data EXIT_SAPMM06E_011 Import Service Prices for Quotation No documentation in English at present.

SRVREL Changes to comm. structure for release of entry sheet Function exits: EXIT_SAPLEBND_003 Change to Comm. Structure for Release Strategy Determination In the standard system, communication structure CESSR (for determination of the release strategy defined for an entry sheet) is filled with the data of the PO, the entry sheet and the entry sheet account assignment. Within function module EXIT_SAPLEBND_003, you have access to the fields of the communication structure. Prior to implementing the strategy determination process, you can therefore change the communication fields in any way you wish, thus influencing which strategy is determined.

SRVSEL Service selection from non-SAP systems Function exits: EXIT_SAPLMLSP_01 Query Whether Selection of Services from Other Systems is Allowed EXIT_SAPLMLSP_011 Call Foreign Selection for Services No documentation in English at present.

CRM00001 Function exits: Development not completed.

User Exits in Customer Relationship Management

4. BAPIs in DetailBAPI_SERVNOT_ADD_DATA This BAPI enables you to add items, causes, activities, task, long texts to a service notification. For more information about necessary import parameters see BAPI_SERVNOT_CREATE (method ServiceNotification.CreateFromData2). Notes: Errors are returned in the parameter RETURN.

BAPI_SERVNOT_CHANGEUSRSTAT This BAPI changes the user status of a service notification. Notes: Errors are returned in the parameter RETURN. Technical note: The user status can be transferred either in internal or external format (fields USR_STATUS-STATUS_INT or USR_STATUS_EXT). If the external format is used, the language must also be specified (field USR_STATUS-LANGU or USR_STATUS-LANGU_ISO).

BAPI_SERVNOT_CLOSE This BAPI is called when completing a service notification. Notes: The notification must have a status that allows the completion. Errors are returned in the parameter RETURN.

BAPI_SERVNOT_MODIFY_DATA This BAPI enables you to modify the header, items, causes, activities, tasks, and partners of the service notification. Notes: Errors are returned in the parameter RETURN. Technical note: If you want to change a field you have to specify the new value of the field in the data structure e.g. NOTIFHEADER-SHORT_TEXT. In addition the corresponding X-structure field e.g. NOTIFHEADER_X-SHORT_TEXT must be checked. If you want to change a partner in the notification, the fields PARTN_ROLE_OLD and PARTNER_OLD must be specified and the Xstructure must be filled as described above.

BAPI_SERVNOT_CREATE This BAPI enables you to create a new service notification. This allows you to create certain fields from the notification header, items, causes, tasks, activities and also long texts for them. Partners can also be maintained. Notes: Errors are returned in the parameter RETURN. Technical note: The sort field must be filled in order to create items, causes, task or activities. When creating a cause the sort field for the item must also be filled. When creating a long text the fields OBJTYP and OBJKEY must be filled. OBJTYP can contain the following values: 1. QMEL - notification header 2. QMFE - notification item 3. QMUR - notification cause 4. QMSM - notification task 5. QMMA - notification activity OBJKEY must contain the corresponding sort field for the above values. The combination of sort field item/cause, item/task or

item/activity must be unique within the same notification. If you leave the sort field blank and OBJTYP = QMEL, the long text is created for the notification header. An external reference key can be transferred by the field REFOBJECTKEY. The links between external reference keys R/3 keys are returned within export table KEY_RELATIONSHIPS. If the fields SENDER, REFOBJECTTYPE and REFRELTYPE are filled, it is possible to create an object link at notification header level.

BAPI_SERVNOT_DEL_DATA This BAPI enables you to delete items, causes, activities, tasks, partners for the service notification. Notes: Errors are returned in the parameter RETURN. Technical note: If an entry has to be deleted, the key of the table entry must be specified e.g. ITEM_KEY for the item to be deleted or PARTN_ROLE and PARTNER for the partner to be deleted.

BAPI_SERVNOT_POSTPONE This BAPI postpones a service notification. Its system status is changed to "Notification postponed". Notes: Errors are returned in the parameter RETURN.

BAPI_SERVNOT_GET_DETAIL This BAPI enables you to display all details for a service notification. Notes: Errors are returned in the parameter RETURN. Technical note: Notification number is a mandatory entry. Information about the structure of the long text table OBJTYP can contain the following values: QMEL - notification header QMFE - notification item QMUR - notification cause QMSM - notification task QMMA - notification activity OBJKEY contains the key of the corresponding object e.g. ITEM_KEY for a notification item. The export structure NOTIFHDTEXT provides additional information about notification header data e.g. description of the corresponding equipment. BAPI_SERVNOT_PUTINPROGRESS This BAPI changes the status of a notification to "in process". Notes: Errors are returned in the parameter RETURN. Technical note: If a notification has the status "open", then the BAPI calls the business transaction "put in process", if a notification is already closed, the BAPI calls the business transaction "put in process again". BAPI_SERVNOT_SAVE

This BAPI enables you to save changes made to a service notification. Notes: Errors are returned in the parameter RETURN. Technical notes: This BAPI calls the update task function of the notification. Afterwards no further changes are possible until BAPI_TRANSACTION_COMMIT is called.

SM Tasks BAPIsBAPI_SERVNOT_COMPLETE_TASK You can use this BAPI to complete a task. Notes: If you use the TESTRUN parameter, the status is not changed. The system checks if the task could be completed by the action. In parameter TASK_KEY, the system expects the key for the task that is on the database. This key can be read in using BAPI BAPI_SERVNOT_GET_DETAIL, for example. BAPI_SERVNOT_RELEASE_TASK You can use this BAPI to release a task for processing. Notes: If you use the TESTRUN parameter, the status is not changed. The system checks if the task can be released. In parameter TASK_KEY, the system expects the key for the task that is on the database. This key can be read in using BAPI BAPI_SERVNOT_GET_DETAIL, for example. BAPI_SERVNOT_SUCCESSFUL_TASK You can use this BAPI to flag a task as successful. Notes: If you use the TESTRUN parameter, the status is not changed. The system checks if the task could be flagged as being successful. In parameter TASK_KEY, the system expects the key for the task that is on the database. This key can be read in using BAPI BAPI_SERVNOT_GET_DETAIL, for example.

PM Equipment: BAPIsBAPI_EQUI_DISMANTLE Using this method, you install a piece of equipment at a functional location at a predefined point in time. If the installation is performed successfully, the method returns the updated equipment data: EQUIMASTER: Structure with equipment master data (EQUI) EQUITIME: Structure with equipment time segments (EQUZ) EQUITEXT: Structure with equipment short texts (EQKT) EQUILOCATION: Structure with equipment location data (ILOA) EQUISALES: Structure with equipment sales data (ILOA) EQUIHIERARCHY: Structure with equipment hierarchy data (EQUZ, ILOA) Notes: Notifications are returned in the parameter RETURN.

BAPI_EQUI_INSTALL Using this method, you install a piece of equipment at a functional location at a predefined point in time. If the installation is performed successfully, the method returns the updated equipment data: EQUIMASTER: EQUITIME: EQUITEXT: EQUILOCATION: EQUISALES: EQUIHIERARCHY: Structure with equipment master data (EQUI) Structure with equipment time segments (EQUZ) Structure with equipment short texts (EQKT) Structure with equipment location data (ILOA) Structure with equipment sales data (ILOA) Structure with equipment hierarchy data (EQUZ, ILOA)

Notes: Notifications are returned in the parameter RETURN.

BAPI_EQUI_CHANGE No documentation in English at present.

BAPI_EQUI_CREATE No documentation in English at present.

BAPI_EQUI_CREATE_BY_REFERENCE No documentation in English at present.

BAPI_EQUI_GETDETAIL No documentation in English at present.

BAPI_EQUI_GETLIST No documentation in English at present.

PM BAPI: Install Equipment (Functional Location, Superior Equipment)BAPI_FUNCLOC_CHANGE No documentation in English at present.

BAPI_FUNCLOC_CREATE No documentation in English at present.

BAPI_FUNCLOC_GETDETAIL No documentation in English at present.

BAPI_FUNCLOC_GETLIST No documentation in English at present.

BAPI_FUNCLOC_SET_LABEL_SYSTEM No documentation in English at present.

Catalog BAPIsBAPI_SERVNOT_GETCATALOGPROFIL You use this method to determine the catalog profile for a piece of equipment for the current date. If the method cannot determine a catalog profile for the equipment itself, the construction type of the equipment, the functional location at which the equipment is installed, the construction type of the functional location, then the catalog profile assigned to the notification type is used Notes: Notifications are returned in the parameter RETURN.

BAPIs for Equipment and Service NotificationsBAPI_EQMT_CREATE With this method, you create a piece of equipment. All data for the piece of equipment to be created can be found in the following structures: EQUIMASTER: Structure containing the master data (EQUI) of the piece of equipment EQUITIME: Structure containing the usage periods (EQUZ) of the piece of equipment EQUITEXT: Structure containing the short texts (EQKT) of the piece of equipment EQUILOCATION: Structure containing the location data (ILOA) of the piece of equipment EQUISALES: Structure containing the sales data (ILOA) of the piece of equipment If the field EQUIPMENT in the structure EQUIMASTER is blank, the equipment number is assigned internally; otherwise the equipment number specified in the field is assigned. Notes: Notifications are returned in the parameter RETURN.

BAPI_EQMT_DISMANTLEFL You use this method to dismantle a piece of equipment at a functional location at a specified time. If the dismantling is performed successfully, the method returns the updated equipment data: EQUIMASTER: Structure containing the master data (EQUI) of the piece of equipment EQUITIME: Structure containing the usage periods (EQUZ) of the piece of equipment EQUITEXT: Structure containing the short texts (EQKT) of the piece of equipment EQUILOCATION: Structure containing the location data (ILOA) of the piece of equipment EQUISALES: Structure containing the sales data (ILOA) of the piece of equipment EQUIHIERARCHY: Structure with the hierarchy data (EQUZ,ILOA) of the equipment Notes: Notifications are returned in the parameter RETURN.

BAPI_EQMT_DETAIL This method reads details of a piece of equipment. The piece of equipment can be identified either by the equipment number (EQUIPMENT) or by a combination of material number and serial number (MATERIAL and SERIALNO). If the piece of equipment specified exists and you have authorization to display the data, the method delivers the details that have been read in the following structures: EQUIMASTER: Structure containing the master data (EQUI) of the piece of equipment EQUITIME: Structure containing the usage periods (EQUZ) of the piece of equipment EQUITEXT: Structure containing the short texts (EQKT) of the piece of equipment EQUILOCATION: Structure containing the location data (ILOA) of the piece of equipment EQUISALES: Structure containing the sales data (ILOA) of the piece of equipment EQUIHIERARCHY: Structure with the hierarchy data (EQUZ,ILOA) of the equipment Notes: Notifications are returned in the parameter RETURN. Technical notes: If you do not want to transfer an equipment number (the piece of equipment is identified by a combination of material and serial number), you must transfer a blank (' ') for the (obligatory) parameter EQUIPMENT.

BAPI_EQMT_GETCATALOGPROFIL With this method, you determine the catalog profile for the current date for a piece of equipment. If the method cannot determine a catalog profile for the piece of equipment itself, for its construction type, for the functional location at which the piece of equipment is installed or for its construction type, Then the catalog profile that is assigned to the notification type is used. Notes: Notifications are returned in the parameter RETURN.

BAPI_EQMT_DISMANTLEHR You use this method to dismantle a piece of equipment from an equipment hierarchy at a specified time. If the dismantling is performed successfully, the method returns the updated equipment data: EQUIMASTER: Structure containing the master data (EQUI) of the piece of equipment EQUITIME: Structure containing the usage periods (EQUZ) of the piece of equipment EQUITEXT: Structure containing the short texts (EQKT) of the piece of equipment EQUILOCATION: Structure containing the location data (ILOA) of the piece of equipment EQUISALES: Structure containing the sales data (ILOA) of the piece of equipment EQUIHIERARCHY: Structure with the hierarchy data (EQUZ,ILOA) of the equipment Notes: Notifications are returned in the parameter RETURN.

BAPI_EQMT_GETLISTFORCUSTOMER This method returns a list of all pieces of equipment for a customer. Only the pieces of equipment that have the transferred customer number (CUSTOMERNO) maintained in their master data are considered. The parameter INT_CUSTMODE controls which of the customer fields are compared. You also have the option of limiting the selection by the equipment type (EQUITYPE), as well as by the material number and serial number (MATERIALFROM, MATERIALTO, SERIALNOFROM, SERIALNOTO). In the table EQUIPMENT, only the selected pieces of equipments for which you have display authorization are returned. Notes: Notifications are returned in the parameter RETURN.

BAPI_EQMT_INSTALLFL You can use this method to install a piece of equipment at a functional location at a specified time. If the installation is performed successfully, the method returns the updated equipment data. EQUIMASTER: Structure containing the master data (EQUI) of the piece of equipment EQUITIME: Structure containing the usage periods (EQUZ) of the piece of equipment EQUITEXT: Structure containing the short texts (EQKT) of the piece of equipment EQUILOCATION: Structure containing the location data (ILOA) of the piece of equipment EQUISALES: Structure containing the sales data (ILOA) of the piece of equipment EQUIHIERARCHY: Structure with the hierarchy data (EQUZ,ILOA) of the equipment Notes: Notifications are returned in the parameter RETURN.

BAPI_EQMT_INSTALLHR You can use this method to install a piece of equipment in an equipment hierarchy at a specified time. If the equipment has been successfully installed, the method returns the updated equipment data. EQUIMASTER: Structure containing the master data (EQUI) of the piece of equipment EQUITIME: Structure containing the usage periods (EQUZ) of the piece of equipment EQUITEXT: Structure containing the short texts (EQKT) of the piece of equipment EQUILOCATION: Structure containing the location data (ILOA) of the piece of equipment EQUISALES: Structure containing the sales data (ILOA) of the piece of equipment EQUIHIERARCHY: Structure with the hierarchy data (EQUZ,ILOA) of the equipment Notes: Notifications are returned in the parameter RETURN.

BAPI_EQMT_MODIFY You can use this method to change a piece of equipment. All data for the piece of equipment to be changed can be found in the following structures: EQUIMASTER: Structure containing the master data (EQUI) of the piece of equipment EQUITIME: Structure containing the usage periods (EQUZ) of the piece of equipment EQUITEXT: Structure containing the short texts (EQKT) of the piece of equipment EQUILOCATION: Structure containing the location data (ILOA) of the piece of equipment EQUISALES: Structure containing the sales data (ILOA) of the piece of equipment The indicator INT_ALL_X shows whether all data fields should be considered for the updates (INT_ALL_X = 'X') or just those in the corresponding flag structures that are indicated as being relevant for updating (INT_ALL_X = ' '). Example: Situation: In the structure EQUIMASTER the data fields EQUICATGRY, EQUITYPE and INVENTORY are assigned values and all other fields are blank IN the corresponding flag structure EQUIMASTER_X the flags QUICATGRY, EQUITYPE and MANFACTURE are set to 'X' and all other flags are blank (' '). Case distinction: If the indicator INT_ALL_X is transferred blank, the data fields EQUICATGRY and EQUITYPE are copied (INVENTORY remains unchanged!) The previous content of MANUFACTURE deleted from the structure EQUIMASTER. If the indicator INT_ALL_X is set to 'X', all data fields are considered and the flag structures are therefore ignored. For the structure EQUIMASTER, this means that the data fields EQUICATGRY, EQUITYPE and INVENTORY are copied And all other fields of the structure are deleted.

Notes: Messages are returned in the parameter RETURN.

BAPI_SERVICENOTIFICAT_CREATE You can use this method to create service notifications. This allows you to create certain fields from the notification header, the long text for the notification header and several notification items. Notes: Notifications are returned in the parameter RETURN. Technical note: The following authorizations are checked: I_QMEL I_TCODE I_BEGRP I_IWERK I_INGRP I_SWERK I_KOSTL

BAPI_SERVICENOTIFICAT_GETLIST This method selects service notifications assigned to a customer. For this, the following data is used as selection criteria: the customer that is maintained in the service notification the notification date whereupon all notifications are selected, whose date is greater than or equal to the data entered You can choose to limit the selection using a partner function and partner number. The service notifications are returned. All notifications are selected regardless of status. You can choose to exclude completed notifications from the selection. Notes: Notifications are returned in the parameter RETURN.

BAPIs for Service Entry Sheets (BO 2091)BAPI_ENTRYSHEET_CHECK This method allows the data of service entry sheets to be checked. Notes: Transfer The entry sheet header data is passed on in the parameter EntrySheetHeader. The account assignments are passed on in the table EntrySheetAccountAssignment. Service data relating to the PO item can be passed on in the tables EntrySheetServices and EntrySheetSrvAccAssValues. Return messages Messages are returned in the table Return.

BAPI_ENTRYSHEET_CREATE You can use this method to create service entry sheets. Notes: The following authorization objects are checked with the activity 76 (entry of services performed). M_BEST_BSA Document type of purchase order of entry sheet M_BEST_EKG Purchasing group of purchase order M_BEST_EKO Purchasing organization of purchase order M_BEST_WRK Plant of purchase order Transfer: The header data of the entry sheet is passed on in the parameter 'EntrySheetHeader'. The account assignments are passed on in the table 'EntrySheetAccountAssignment'. The service data for the service entry sheet can be passed on in the tables 'EntrySheetServices' and 'EntrySheetSrvAccAssValues'. All value and price fields are to be passed on in the currency of the purchase order. Return messages: Messages are returned in the table 'Return'.

BAPI_ENTRYSHEET_DELETE You can use this method to delete entry sheets. Notes: The following authorization objects are checked with the activity 76 (entry of services performed): M_BEST_BSA Document type of purchase order (of entry sheet) M_BEST_EKG Purchasing group of purchase order M_BEST_EKO Purchasing organization of purchase order M_BEST_WRK Plant of purchase order Messages are returned in the table 'Return'.

BAPI_ENTRYSHEET_GETDETAIL You can use this method to output the detailed data on a service entry sheet. Notes: The following authorization objects are checked with the activity 03 (Display): M_BEST_BSA Document type in purchase order M_BEST_EKG Purchasing group in purchase order M_BEST_EKO Purchasing organization in purchase order M_BEST_WRK Plant in purchase order Error handling: If error messages are issued during the processing, they are returned in the table 'Return'. This table also logs information messages.

BAPI_ENTRYSHEET_GETRELINFO This method allows you to output detailed data on the release status of the service entry sheet.

BAPI_ENTRYSHEET_RELEASE This method allows you to release entry sheets. The entry sheet number and the release code must be passed on. The new release status and the new release indicator are returned. Notes: The authorization object M_EINK_FRG is checked. A COMMIT WORK is set in the module.

BAPI_ENTRYSHEET_RESET_RELEASE This method allows you to cancel the release of entry sheets. The entry sheet number and the release code must be passed on. The release status and the release indicator valid prior to the release are returned. Notes: The authorization object M_EINK_FRG is checked.

BAPI_ENTRYSHEET_GETLIST This method allows you to list service entry sheets. You pass on the desired selection criteria (e.g. purchasing group, plant, vendor) Work, Supplier in the import parameters. For more information, refer to the relevant parameter documentation. Notes: The following authorization objects are checked with the activity 03 (Display): M_BEST_BSA Document type in purchase order M_BEST_EKG Purchasing group in purchase order M_BEST_EKO Purchasing organization in purchase order M_BEST_WRK Plant in purchase order Return: The entry sheets that satisfy the selection criteria are returned in the table 'ENTRYSHEET_HEADER'. Error handling: If error messages are issued during the processing, they are returned in the table 'Return'. This table also logs information messages.