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

Similar Messages

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

Release startegy of Service Entry Sheet

I configured release strategy for Service entry sheet with Release code 08.
When i actually go to ML81N to release the same, i get same code in the drop down but when i select the same (08), it gives me "error Release with code 08 not possible", instead it allows only to release the same with Release code R1 which is the code for Purchase Requisition.
What could be the problem ?
Regards,
Shail

Hi,
I have just configured two release strategies for entry sheet's and they work correctly in our development sandpit. when I moved these to the test client, the config is showing correctly but the internal tables have not updated properly.
This gives me the same error, but that is because the system cant actually find the release code.
Is this the same problem you are having? If so I can post the solution for you.
Cheers,
Tim

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

Release stratedgy of service entry sheet

Hi,
I have created release stradegy of service entry sheet.
I have created
Group Y1 and Release Strategy 1 (General) the Release Codes FR in the first line and AB in the second line.
On the Prerequisites dialog box I have marked the small box AB in the second line .
On the Release Statuses dialog box, I have defined the Release Statuses as under.
FR     AB     Release indicator
          N = Not accepted
X          B = Order placed
X     X     A = Service Accepted
but when *I simulating the stratedgy it is showing pre requisite AB is missing.*
*I have checked AB but FR is showing checked in release status dialog box.*
*In me81n release is possible only for FR.* is showing .
How I can have release first AB then FR.
pl help.
SB

Hi,
please check the table T16FV for the release sequence - prerequisits..
The design is: if there are prerequisite codes necessary for some release step it can always be just one prerequisite code per level.
1) You work with release code AB and FR: Please check how many Persons are
authorized to release with AB or FR.
2) If you don't use any prerequisites: AB and FR can release at the
same time.
In customizing (release statuses) you assign release indicators as
follows (example):
AB FR                Release indicat
X                        B
        X                 N
X     X                 A
All other combinations will have release indicator N(blocked).
This way you can guarantee the entry sheet can just be
released if both AF and AB released.
Regards,
Edit

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.

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..

Work Flow for Service Entry Sheet

Hi all,
We need Work Flow for Service Entry Sheet as below using SAP mail box :
Once Created, will go to Incharge for varification.
If yes, will go to Manager for further varification.
If yes, will go to again Incharge back for Release.
Regards,
Hamadeh Bashir
Gulf Petrochemical Industries Company,
Bahrain

Hi,
Object Type BUS2080 (Service Notification)
Standard Task TS00008336 (Processing a Service Notification)
Workflow Template WS00200099 (Putting a Service Notification in Process)
You can define your own workflow.
Regards,
Srilatha.

MIRO invoice verification for Service entry sheet

When trying to do invoice verification for Service entry sheet i am getting this below error pls guide me
Delivery note/service entry sheet 5000000150 does not exist
Message no. M8183

Hi,
You may be saves SES number and now SES is not released!
1st Just cross check PO history TAB of service PO(ME23N), did you have only service entry sheet number or you have service entry sheet number and material document( will be created after releasing SES) with 101 movement type.
You have created service entry sheet (SES) in ML81N and got SES number, so as to recognize the vendor performed service. Next step, you need to accept service by releasing SES( in ML81N by clicking green flag or if release strategy there for SES, you need to release SES in ML85) so that FI document will be created.
Once SES released, then you can do MIRO w.r.t SES only.
Check doc:
http://help.sap.com/bp_bl604/BBLibrary/Documentation/209_BPP_EN_FI.doc
Regards,
Biju K

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

Manual for service entry sheet and service master

hello all,
if someone is having manual available for service entry sheet and service master....
regards,
Rahul Bhardwaj.

You have to configure service category in SPRO for service master and you can assign the number range in SPRO
The path is SPRO is:
Materials Management-External Services ManagementService Master---Define Service Category
Service Master is created using AC03
The service master record counts as part of the master data within External Services Management and serves as a source of data for you to draw upon when creating service specifications. This enables you to save time and reduces the frequency of errors, since you need only enter the complete service descriptions in the service master record once.
A service master record contains the following principal information for the unique description of a service:
Service number
Service category
Descriptive texts (short and long text)
Base unit of measure
Material group
Valuation class by which G/l account is determined
when you reference it in the PO, all the data gets transfered and you avoids the mistakes

Supress Mandatory field for Service Entry Sheet Creation

Hi,
I am using BDC for Service Entry Sheet creation as BAPI cannot fulfill the Business needs.
During Recording when I click on Service Overview and click on Service Selection we provide the Model Service Specification Number there I can see the Services and select it, but when I select the service and adopt, an error message ocuured to enter the quantity.
Is there any way to supress the standard error message without using acess Key.
BR
Aviram

Hi Aviram,
Messages type 'E' , 'I' or 'W' are controlled through configurations. Please check with your functional consultant with the message number you want to supress. It can be made as 'I' or 'W' through configuration.
Similarly if you do not want that particular field as mandatory field ask functional consultant to make it optional.
Regards
Sachin
Edited by: sachin G patil on Mar 9, 2011 3:13 PM
Edited by: sachin G patil on Mar 9, 2011 3:20 PM

Output determination (print out) for service entry sheet

All SAP Gurus,
What are the steps involved in determining the output (print out) for service entry sheet?
Regards,

Hai,
Goto NACE select the Application ES, out type NEU and maintain the program SAPFM11, Formroutine ENTRY_NEW, form ML_SERVICE_ENTRY aganist medium printout and maintain the condition records for printout to VN.
take print in ML83
Regards,
eswaramanu...
Edited by: eswar manu on Oct 21, 2008 8:37 AM

Create number range for Service Entry Sheet (SES)

I would like it is possible to configure the number range for Service Entry Sheet (SES) or it is fixed in the system? Besides, for my current configuration, the number only appear when SES is done but no reversal number if I reversed the SES, is this a correct setting? Or is there any way I can set the number for reversal document?

Hello,
Check below SAP link.
http://help.sap.com/saphelp_40b/helpdata/fr/77/e12c7dd435d1118b3f0060b03ca329/content.htm
Hope it will help. Revert back if anyfurther question/s.
Regards,
Anup

Table for service entry sheet quantity

Hello,
I know the table for service entry sheet detail is ESSR.
I want to find out the qunaity which i booked in service entry sheet from table.
I am not able to get it. I tried table ESLL. But still it does not show the quantity.
Please guide me to the table name in which when i put service entry sheet no , i will get the quantity
Thanks
Nilesh

hi,
FRom ESSR table for the corresponding po , find out package no .Then the pass the same package no in table ESLL table where you can get the desired service qty.
Regards,
velu

Release Procedure for Service Entry Sheet Wr to the Purchasing document

Similar Messages

Maybe you are looking for