External Services Management (MM-SRV)

[bholus9]

Collective Release of Service Entry Sheets


Use
Simplification of the release procedure through the automatic generation of a list of entry sheets awaiting release for a certain employee.


Type of Internet Application Component


Intranet

If a service entry sheet fulfills certain criteria (e.g. the value exceeds $20,000) it needs to be approved before it can be accepted. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".


Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code.



Releasing (approving) service entry sheets like this in the R/3 System necessitates detailed knowledge of the system and cannot always be done without prior instruction.



The approver must be able to navigate in the R/3 System, know his or her release code, and work through a number of different screens.


With its easy-to-use browser interface, the Internet Application Component (IAC) Collective Release of Service Entry Sheets considerably simplifies the process of approving entry sheets for services performed.



The system automatically generates a list of the service entry sheets that the user has to process with his or her release code (it is not necessary for the user to know this code).



All that then has to be done is to choose an entry sheet from the list and release it. It is also possible to cancel (reverse or revoke) a release that has already been effected.


Working with this component is particularly convenient for employees whose daily duties include other tasks in addition to the release (approval) of service entry sheets
.
Advantages of the Internet Application Component

• No training necessary - thanks to the easy-to-use, self-explanatory user interface. Knowledge of the R/3 transaction for releasing (approving) service entry sheets is not required.
• Virtually no possibility of errors.

Prerequisites


Authorizations/Security


The following authorizations must be assigned to the user who releases service entry sheets:

Authorization object	Description
M_EINK_FRG	Release code and group in Purchasing

Standard Settings and Default Values


The following settings are necessary before you can work with the Internet Application Component:

• A release procedure for service entry sheets must be active, and entry sheets requiring release must exist, in the R/3 System.
• The following parameters must be stored in the SAP user master record:

• • FAB (release code the user works with)
  • FGE (release group to which the release code is assigned)

Features


Differences Between this IAC and the R/3 Transaction for the Collective Release of Service Entry Sheets


The R/3 transaction is considerably more extensive and provides more input fields and functions. Among other things, this Internet Application Component does not include the following R/3 standard transaction functions:

• Change entry sheet data (blocking indicator, "delivery completed" indicator)
• Release all entry sheets at the same time

Activities


R/3 Development Objects and Customizing Options


The data recorded in the Intranet is passed on to the R/3 System via Business Application Programming Interfaces (BAPIs). A simplified R/3 transaction with screens has been created for the Internet Application Component, involving the following development objects:

Transaction:	MEW7
Program:	SAPLMEW4
BAPIs (with function group):	EntrySheet.GetDetail (MLBO) EntrySheet.GetList (MLBO) EntrySheet.Release (MLBO) EntrySheet.ResetRelease (MLBO)

Service Name


The service name of this Internet Application Component is MEW7. You can find all the relevant data under this service name in the SAP@Web Studio.

In addition to the possibility of changing the layout, this Internet Application Component provides a number of other adjustment options.


Any change made to the R/3 development objects used for the Internet Application Component counts as a modification.
Under no circumstances should you change the development objects themselves.
The following options are available if you wish to create a transaction of your own based on the Internet Application Component of the standard system:

• You use less than the functionality offered (by deactivating fields)
• You use more than the functionality offered

For this purpose, you analyze the possibilities afforded by the SAP transaction MEW7 using the ABAP Workbench and add the desired further possible uses to your Internet Application Component.


You can create a completely independent transaction with other screens. If you do so, you must satisfy the technical preconditions for Web transactions. You can then design your own Web pages.