Report for Service Eetry Sheet Release Status

I have created a Service Entry Sheet which has 4 Levels of approval. How will I come to know which level is completed and which one is pending?
Is there any standard report available?

Hi,
then create z report
use
     ESSR-FRGGR - release group
     ESSR-FRGSX - release strategy
     ESSR-FRGZU - release status
     ESSR-FRGKL - release indicator
     ESSR-FRGRL - release not yet completely effected
Regards
Kailas Ugale

Similar Messages

Report for Service Entry Sheet in MM

Hi all,
Is there standard data source & infoproviders are available for "Service Entry Sheet (ML81N)".
We need to develop a report for service receipt confirmation along with PO & Vendor payment details.
Looking forward your answers.
With regards,
MK.

HI,
Yes, WBS wise PO details showing in T-code ME2J - Purchasing Document Per Project .
Enter the above T-code and select Database Profile ' 000000000008-PO Display for WBS' then give inputs project code,WBS Element,plant,Scope fo List-'ALV'.and execute the report. Now, report showing the selected WBS Purchase documents.
Hope, it is useful for you.
Regards,
K.Rajendran

MM Service Entry Sheet Release Problem - Plant Not Considered

Dear Experts,
I have a problem in Service Entry Sheet Release as it does not consider plant although it is maintained in Release Strategy.
I have created 1 Class for Service Entry Sheet Release.
This class contains 3 Characteristics, 1st for Plant, 2nd for Value of Services and 3rd for Purchasing Group.
Now the problem is that during the Entry Sheet Release, system does not consider the Plant in deciding the Release Strategy.
It considers the first Release Strategy found for Purchase Group and Value of Service combination, thus ignoring the Plant Characteristic.
Characteristic for Plant is having 'Released' Status
Please suggest what to do so that the Plant is also considered in Release Strategy.

Dear Charlie,
Thanks for your reply.
When I go to CL40N and check then system gives correct Release Strategy as it considers plant there.
But when actually the Entry Sheet is created/saved then system gives wrong release strategy as it does not consider Plant.
Let me tell you that my Release Strategies do contain common Purchase Groups but the Plants are different. So each Release Strategy is unique in this way.
But during Service Entry Sheet Creation system does not consider Plant in determining Release Strategy.
Please Help.

Service Entry Sheet Release Procedure

Dear all,
I want to assign a new Plant to an existing service entry release strategy. In CL20N for Class Type 032 and maintaining the Release Group and Release Strategy I want, I hit ENTER and the Class SERVICE_RELEASE is displayed, which is correct (it is a service entry release procedure).
Selecting the item and displaying the values for the Class, I have Plant, Order Type and Cost Centre. I added a new row, include a new Plant and hit Save. I get the message "Saving changes to assignments" and then I exit the screen.
However, to double check that the object has been assigned to the class, I check in SPRO>Materials Mgt>External Services Mgt>Define Rel. Procedure for Service Entry Sheet> Release Strategies to confirm that the object was created in the classification for service entry release procedure. BUT IS NOT THERE!
However, if I performed the assignment in Classification in SPRO for the release strategy, and check in CL20N, IT IS THERE!!
How come I have created in CL20N and it is not displayed in SPRO for the same release strategy? The object assignment was successful with no error msg. It is not possible that you have done it in CL20N and you have to do the same in SPRO, right? Doesn't serve the purpose..
Pls help.
Thank you.

Dear Sir,
Go to CL02 give the Class and Class type, click on change icon
Copy the characteristic of Plant from Char. Tab
Then Go to CT04
give characteristic which is copied from class and click on change icon.
enter your new plant in Values tab, Save back
Go to CL20N, give release group and release code for which you want to maintain the new plant.
give the plant and save enter.
i hope this will help you.

Best Practices for Service Entry Sheet Approval

Hi All
Just like to get some opinion on best practices for external service management - particularly approval process for Service Entry Sheet.
We have a 2 step approval process using workflow:
1 Entry Sheet Created (blocked)
2. Workflow to requisition creator to verify/unblock the Entry Sheet
3. Workflow to Cost Object owner to approve the Entry Sheet.
For high volume users (e.g. capital projects) this is cumbersome process - we looking to streamline but still maintain control.
What do other leaders do in this area? To me mass release seems to lack control, but perhaps by using a good release strategy we could provide a middle ground?
Any ideas or experiences would be greatly appreciated.
thanks
AC.

Hi,
You can have purchasing group (OME4) as department and link cost center to department (KS02). Use user exit for service entry sheet release and can have two characteristics for service entry sheet release, one is for value (CESSR- LWERT) and another one for department (CESSR-USRC1) .Have one release class for service entry sheet release & then add value characteristics (CESSR- LWERT) and department characteristics (CESSR-USRC1). Now you can design release strategies for service entry sheet based on department & value, so that SES will created and then will be released by users with release code based on department & value assigned to him/her.
Regards,
Biju K

Workflow in Service Entry Sheet Release

Hi Friends,
Can we activate workflow for Service entry Sheet Release. How many levels can we take in this , I mean release Strategies.
We activated for PO / PR.
Pls. let me know the process / details where can I get more info on this.
Regards
Sai Krishna

Hi,
If you want to subject release strategies for SRM confirmation/service entry sheets in backend system, then it would not be possible as the service entry is created and released simultaneously. However you can achieve this, if you switch to different Bapi for SES posting.
For more info in abckend system, Go to SPRO setting MM>External Service management-->Define Release strategy for SES.
Regards,
Sanjeev

MM - ML81N, Release Procedure for service entry sheet

Hi Gurus,
I would like to active the realease strategy for service.
in order to customize I set:
-Relase Groups
-Release Codes
-Release indicator
-Release startegues
Then I run ML81N TRX and I called a sheet to try. This sheet had to has done to one of the release strategy set...
on the menu (of this trx ML81N)Entry Sheet->Set Status->Release (is still turn off)
Where is the problem?, anybody could help me?
Tks in advance,
Nacho

Hi,
please read the FAQ note 672719, question 5:
Setting up a release procedure is explained in the following short
example: All service entry sheets with material group 007 are supposed
to be subject to a release strategy. This release strategy requires that
the service entry sheets must be released with release code A1. Only the
cost center manager has the authorization for release code A1.
A) Create a characteristic for the material group:
o Call Transaction CT04. (Path in the SAP menu in R/3 Enterprise:
       Cross-Application Components -> Classification System -> Master
       Data -> Characteristics)
o Specify a name for the characteristic, for example CESSR_MATKL,
       and choose the 'Create' pushbutton.
o On the 'Basic data' tab page, enter a description and keep the
       'Released' status.
o On the 'Addnl data' tab page, enter table name CESSR and field
       name MATKL (Material group).
o Enter class type 032 (Release strategy) on the 'Restrictions' tab
       page and then save the characteristic.
Note: The release strategy must be based on a field of structure CESSR.
Using Transaction SE11, you can display which other fields are available
in addition to the material group (field MATKL).
B) Create a class to which you assign the characteristic:
o Call Transaction CL02. (Path in the SAP menu in R/3 Enterprise:
       Cross-Application Components -> Classification System -> Master
       Data -> Classes)
o Enter a class name, for example FRG_ESSR, and class type 032 (for
       release strategy) and then choose the 'Create' pushbutton.
o On the 'Basic data' tab page, enter any name. (Keep the
       'Released' status.)
o Enter characteristic CESSR_MATKL on the 'Char.' tab page and then
       save the class.
C) Now carry out the required Customizing settings. Follow IMG path
(Transaction SPRO) 'Materials Management -> External Services Management
Seite 4
-> Define Release Procedures for Service Entry Sheet'
o At first, you must create a release group (for example 03). For
       that, choose 'Release Groups', then choose 'New Entries', enter
       'Rel. Group' = 03 and 'Class' = FRG_ESSR. Save the entry. The
       system automatically determines value 3 (for entry of services
       performed) for the release object.
o Now create release code A1 for release group 03. Choose 'New
       Entries' and specify the following values: Grp = 03, Code = A1,
       and description, for example cost center manager.
o Create two release indicators, for example A and B. Select the
       'Released' field for release indicator B and save the entries.
       (Note: A release strategy must at least contain two release
       indicators. The first indicator (here A) must be defined as
       locked, the last indicator as released. Furthermore, the general
       changeability of the service entry sheet and the behavior for
       value changes are defined via the release indicators.)
o Finally create the release strategy. Choose 'New Entries' and
       specify the following values: Release group = 03, release
       strategy, for example RS, release codes = A1. Assign the two
       release indicators A and B via 'Release statuses'. Assign
       material group 007 via 'Classification'. Save the release
       strategy.
D) Assign the authorization for release code A1 and release group 03 to
the cost center manager. In role maintenance (Transaction PFCG), you can
for example use the default values for Transaction ML85 for that.
Regards,
Edit

How to generate report for Service sheet - ECC 6.0

Hi
Can anyone let me know regarding how to generate reports for service sheets entered
regards
Sanjay

Hi,
Get Service Entry Sheet with following T.codes:
1.MSRV6
2.ML84
Regards,
Biju K

Release Procedure for Service Entry Sheet Wr to the Purchasing document

Hi,
I have configured the Service entry sheet release procedure on the basis of Purchase order document type by creating Characteristic With table -field (CESSR - BSART) and also class is maintained where the defined characteristic has been assigned.Release group is assigned to the class and all necessary customizing activities carried over. I assigned release group n Strategy thru Cl20n and also checked in Cl30n for the document type where system is exactly proposing only one value for the document type. But when i create Service entry sheet thru ML81N after saving the document i checked for release strategy through Goto-> Service entry sheet -> Release Strategy which is grey mode.
I tried thru ML85 System says that no suitable purchasing document is available for release.
thank u
Nagarjuna
Edited by: yalamanchi nagarjuna on May 31, 2009 1:33 PM

the same configuration is not working in DEV environment but working fine in Quality and PRD

User names of service entry sheet release strategy

Dear Expert ,
Kindly guide from which table could I get the user names values who done the release strategy for service entry sheet for example I have 3-release codes : 1. Creator
                        2. Verifier
                        3. Approver
So I need to know who has done these 3-actions for respective service entry .
Best Regards

Hi,
The information about the Person who has relesed the entry sheet will be not stored in the change document for the entry sheet.
There is only the information about which release code has released the SES. In an organization a certain user or a group of   users can use the very same release code.
However, if you have also configured a workflow with this release strategy, then it is possible to know who has
released the SES.
You will need to create you own report which reads the change history (CDHDR and CDPOS) and finds out the date when the last release code of the release strategy has been released and to find out based on this data who was the approver.
Regards,
Edit

Service entry sheet release flag is not appearing in the change mode.

Hi,
In Service entry sheet release flag is not appearing in the change mode(ML81N). though release strategy is exsists in the header level.
note:
1.No changes done release setting, classes, or any other parameter.
2.Last day Few service entry sheets have been released by user .
3.And also i tried with different user , whereas he is geeting release flag, but concern user is not getting?
wht could be reasons?
Please provide suitable solution.
regards,
kumar.

Issue here is user is having authorization issue. Please run ML81N and execute /NSU53 report.
Also execute ML81n and then /NSU53 report for the other user whos does not have this problem. Then send both the reports to Security team asking them to add the missing object in the user's role who has the problem.
Hope this helps.
Ganesh

Approving Partial Quantity in ML85 for Service Entry Sheet

Hi,
Is it possible to approve partial quantity in ML85(or any other screen) for Service Entry Sheet?
Thanks.

Hi,
I dont think it is possible to approve Entry sheet for partial quantity. Release strategy for Entry sheets are at Header level and not item level.

Reports for service entry

Hi Experts,
Can anybody please tell me,
1.Report for Pending PO's those not created Service Entry Sheet.
2.Report those showing Cost Center and GL Ac with entire history for Service Entry Sheet.

Dear,
I give only one answer of your question.
Report for Pending PO's those not created Service Entry Sheet.
ME2N is display only those PO for which service entry sheet is not created.It not display service entry sheet number or any other detail.
Regards,
Mahesh Wagh

Service Entry Sheet Release Strategy

Dear Friends,
We are re-configuring Service entry sheet release strategy. My client wants 4 level release strategy like ,
Level 1 (0-10 lacks )
Level 2 ( 0-50lacks)
Level 3 (0-100 lacks )
Level 4 (> 100 lacks )
I have created release group, with release object3.
I have created 4 release codes and 4 release strategies.
We have so many departments like commerciual, safety, HR, Projects.
My client wants only 4 codes to be created. My problem is that, how each and every departments HOD can release SES ? How I can control SES of his department to be released by him ?
Please help.
With Best Regards,
Rajesh

Hi,
I've configured release strategy department wise(HOD's)
For that you need to create new characteristic for Tracking number.
You can enter tracking no such as HR,PRD, PUR etc.
Now maintain these tracking no in classification.
Release will work as per respective HODs.
Seems bit lengthy but I found it very useful.
Try it.
Regards,
Piyush

SRM-SUS for Service Entry Sheets - Classic Scenario

Hi SRM Gurus,
Our client wants to use SRM-SUS for the Service Entry Sheets (to being with and then later expand more in other SRM areas). The lead system will be R/3 system.
We will be going with ECC 6.0 and SRM 5.0.
Service Order will be created in R/3 and replicated into SRM (SAP have said this is new functionality in SRM 2007 and SAP will provide us with this functionality in SRM 5.0 as well)
SAP are also recommending using MDM for hosting the catalogs for service entry sheets to enable vendors to selete their items during the confirmation / filling the service entry sheets. - they say this is mandatory
SAP are also asking for XI for the data to be transferred from R/3 to SRM (and may be vice versa) - they say this is mandatory.
Few questions:
1) What kind of hardware size are we talking about to have SRM-SUS, MDM, XI and Portal (PI)
2) Are MDM and XI mandatory as said by SAP and if yes, in what scenarios. What is they way around
3) How good is the functionality provided by SRM-SUS for Services? Is it as good as in R/3 (or even better)? We will be having complex Services in our scnearios.
4) What can be a typical time to install SRM-SUS, MDM, XI and Portal in the Dev environment to get moving onto the project?
An early response shall be highly appreciated.
Thanks in advance
Regards
Rahul

few answers to your questions
1) what is the release of SRM you want to work with?
2) services in SUS is not available as standard , and will be provided by SAP as consulting up on request.
3) for hardware requirements , please refer to the master guide for the srm release you will be working on -->
and also you can refer to the software component matrix in master guide --> to see if any component is mandatory..
4) XI and MDM as far as i know is mandatory for SRM 6.0 and above , But in SRM 5.0 , XI is compulsory.
5) so xi is mandatory in anyway in SUS as different systems are involved and therefore is required for routing the documents correctly.
6) time for installation again depends on your supplier base , and your level of expertise.
7) it is not always recommended to compare between two different systems , R/3 and SUS are different and so functionality will not be the same
8) but as far as i know R/3 is stronger functioanlly..

Report for Service Eetry Sheet Release Status

Similar Messages

Maybe you are looking for