Release strategy for Negative Service Entry in ML81N

Dear Gurus,
I have one requirement like when my user will do negative entry in service entry sheet it should go for approval or else I want to allow certain users to do negative service entry. How to achieve this ?
Thanks in advance
Regards
Chinmaya

The user exit EXIT_SAPLMLSP_031 in the project SRVESLL contains the line item data.
The table SRV_ESLL will contain all the service related information along with its quantity.
Here you will be able to identify the line items containing -ve Quantity.
After identifying the line items with the negative quantity you can check if the user ID of the current user is authorized to create -ve Quantity or not and raise an error message if the user tries to release the Service entry sheet.

Similar Messages

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

Autorisation object for accepting service entry sheet in ML81n

Dear Sapiens,
What is the authorisation object for accepting service entry sheet in ML81n, here with my client some users are not getting the acceptance flag.
kindly guide.
Viji kantha

Hi,
I would like to share with you additional information on activities 75 and 76 to the different release objects:
To accept the service entry sheet the user has to have both
activities 75 and 76. Please note that it is not possible to accept an entry sheet
without activity 76.
Activity 76 means maintain service entry sheets,
Activity 75 means accept service entry sheets.
In order to accept the entry sheet, you must change into the
change mode. In order to change into the change mode, you
need the activity 76.
This activity 76 will be used in both creating and changing of the
entry sheet.
Regards,
Edit

No release strategy for service PO

Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
Shailendra

Keep the release strategy at Plant level only....All the purchasing docs will get blocked

Approval for revoking service entry

Hi All,
I have one requirement that system should ask for approval of manager if the user revokes the service entry. Currently there is no release strategy for service entry in the system as the user is only creating and accepting the service entry sheet. They are fine with this, but if user revokes the already accepted service entry then it should ask for manager approval.Is it possible.
Thanks.

Hi,
This is not possible as User have full authorization to revoke the service entry sheet.
But you can try based on workflow.Do check with workflow consultant whether he can add an logic.
Custom workflow for releasing service entry sheet

Release strategy for PREQs created from PM work order

Hi All,
I have an issue with determining release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
We have activated release strategy for Purchase requisition based on the following characteristics:
CEBAN_PLANT
CEBAN_COST_CENTER_GROUP
CEBAN_MANUAL
Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding cost center goups.
In the user exit we have consider to cases:
The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
We have defined for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
Best Regards,
Desislava

Hi,
For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
Regards,
Raj

Assignment Feild in Service entry sheet - ML81N

Dear All,
We need to add assignment Feild (ZUONR) in Service entry sheet (ML81N).
Can any one suggest the posssible solution.
Thanks & Regards

Hi JKTECH TEAM ,
As a standard process , system is not going to given Assignment field as input field for ML81N. you can use reference or Document header text.
If you required you can use reference or Document header text or you can use user fields.
If you still required you need to maintain customisation through Exits :
INTERFAC            Interface for data transfer
SRVDET              User screen on tab strip of service detail screen
SRVEDIT             Service list control (maintenance/display)
SRVENTRY            Unplanned part of entry sheet (obsolete since Rel. 3.1G)
SRVESI              Data conversion entry sheet interface
SRVESKN             Set account assignment in service line
SRVESLL             Service line checks
SRVESSR             Set entry sheet header data
SRVEUSCR            User screen on entry sheet tabstrip
SRVKNTTP            Setting the account assgnmt category when reading in, if "U"
SRVLIMIT            Limit check
SRVMAIL1            Processing of mail before generation of sheet
SRVMSTLV            Conversion of data during importing of standard service cat.
SRVPOWEB            Purchase order for service entry in Web
SRVQUOT             Service export/import for inquiry/quotations
SRVREL              Changes to comm. structure for release of entry sheet
SRVSEL              Service selection from non-SAP systems
Please choose your choose.Because Assignment field is given for Sorting purpose of any documents

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

Dump during creation of service entry sheet (ML81N)

Dump during creation of service entry sheet (ML81N)
Hi,
ML81N>Select PO>Enter>goto entry sheet create (empty page)>service entry sheet displayed with internal no. assigned >click tab "service selection">Input PO No.--> enter (here we get Dump ABAP RUNTIME ERROR "TABLE_INVALID_INDEX").
This is happening only for some POs. What can be the problem?. Is this has something to do with SAP database ???
- rahul

Hi,
it could have the cause that the note 1113220 was missing from your system or that data are inconsistent in your PO.
If you implemented 1113220 and you still get the dump, please check in transaction ST22 the run time error long text to the dump:
Parts:
- How to correct the error?
- Information on where terminated
- Source Code Extract -> if you set a breakpoint before the line where the error occured, you could debug the process.
- Active Calls/Events: if you have an own program displayed here, please check first your program wether it has caused the issue.
If these do not help to find out the problem cause, please open a SAP ticket and include all of the relevant information regarding the dump.
Regards,
Edit

Release strategy for PR with multiple item category

Hello,
I'm trying to create a global release strategy for a PR based on the item category. I have defined a caracteristic with different item categories (A and K).
If I create a PR with item category A, the correct strategy is triggered as well as for an PR with item category K. The problem is when I create a PR with 2 positions, one A and one K, there is no strategy triggered.
How can I change my settings that there is also a strategy triggered in this case ?
Thank you in advance for you help.
Kind regards

Hi,
Solution is very small. Please maintain a blank entry too in the characteristics value. It will start working.
Sanjeev

Release strategy: Tx CL20N Error: Entry 01 does not exist in table T16FS

Dear MM Gurus,
I was designing new release strategy for PR and PO, so I deleted all the previous entries(SPRO) available in SAP. I created my new entries but in the transaction CL20N I got the above mentioned error: "Entry 01 does not exist in table T16FS-Check your entry" . I checked the table T16FS, where the entries were available. It also showed the previous entries I deleted from SPRO.
Refering the SAP note 365604 (version 29, valid from 08.10.2008), I created the deleted entries again so that I could delete them in the required sequence
1. release strategies
2. release indicators
3. release codes
4. release groups
5. class
After deleting the entries in the above mentioned sequence also I am getting the same error in CL20N.
I ran report RCCLZUOB, it shows the entries does not exist.
Please help.
Edited by: Akshay Kurhe on Mar 2, 2009 6:02 AM

hi
check this setting
Distribution Using Object Classes -->Maintain Class Types & Maintain Classes

Redetermine release strategy for purchasing requisitions

Hi Guys,
How can I redetermine the release strategy for purchasing requisions when changes on the costcenter (EBKN-KOSTL) are done -
I know that it will be redermined when I add the costcenter as charateristics in customizing for release strategy but thats not an option
I also tried to add coding in userexit for changing the communication strategy (Include ZXM06U13) but this exit doesn't provide information of the document number and position (EBAN, EBKN ..) so I can't find out if changes have been made
I spend several hours trying to find solutions for this issue but no working results so far ..
I hope you can help me on that
TIA
Manuel

Hi,
Note that EBKN will have entries corresponding to a PR only when it is
saved or checked, so KOSTL will not have any values for a PR which is under
creation. You should always use fields from structure CEBAN while
creating characteristics for Requisition release procedure as it
contains most of the relevant data about a PR under creation/change.
I would advice you to check the note 365604.
Please also check the changeability indicator in the customizing:
transaction OLME -> Purchase Requisitions -> Release Procedure -> Procedure with Classification -> Set Up Procedure with Classification -> Release indicator -> check the detail screen for settings.
Please check additionally the possible values for your characteristic cost centre (transaction CT04).
Regards,
Edit

Release strategy for GR?

Hi,
My company has requirement that GR should be subject to approval process before it can be posted. As far as I know there is no standard functionality in SAP for this (at least in ECC, as in SRM there is one).
Has anyone encounter this before? And how you deal with this? I have tried to persuade the user to drop this, but the problem is they already have this functionality in their legacy (which is custom made web based application), so it is pretty hard to argue with them in this area.
Any help will be appreciated.
Best regard

Hi Yosea,
Yes you said is right that there is no Release strategy. And can't imagine the situation in the legacy as well for this approval process thru Release strategy while doing the GR. But there is another way of accepting the goods either partial or full using movement types, you can do so.
My question is why do you (i.e., your client or company) want to control (through the approval process) at Goods receipt level. That makes complex and un logical as well, thats why there is an approval process comes into picture at PO (Purchase order is an external purchase document and is going out to an external party /vendor /supplier) against that they can supply the material /provide the services to the Organization/company and is required to control before issuing this perticular document called PO (i.e., work order and is required to be controlled thru Electronic release strategy in SAP) instead of manual before in legacy since there is money matter involved and needs to control over investment on Inventory /services purchases.
But where as GR, this is an incoming document, what the meaning in controlling it through approval process. That is the way you have to conveincene the client or company.
Ok fine. If still they want this functionality to be implemented (that is to controlling at the GR level for the goods coming in. Then there is another way to control it through receiving the stocks into different stock types using the respective movement types, but not through Release strategy such as Blocking (GR blocking), Quality stock (for checking the quanlity standards thru Quality Inspection) and then later you can move these stocks to Unrestricted use stock, so that this can be allowed to use further.
I dont think there is a functionality in the SRM as well. As I know that you can receive the Goods in SRM through Online Desktop confirmation that too partial or full quantity, that is nothing accepting/approval for the Partial or full quantity that is received against the PO which is created wrto to respective Shopping cart. And that is how you can control the goods that are coming inside / received at Stores/WH inorder to maintain the good quality of Inventory.
Note: Controll always suggested at the time of making agreement (i.e., Release strategy for the PO) but not at the time of receiving the goods. Here while receiving the goods only thing that a Stores person can see tmainly is needs to check for the Quantity, Quality of the goods that are ordered, Delivery time, Mode of transport, Shipping instructions, etc. This will help them further in evaluating the vendor.
Hence there is no logic is going for that option
Hope it clarifies,
Regards,
Sapsrin

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

Release strategy for quantity contract

Hi Gurus,
In quantity contract .. target value will not filled by the value(in header details) as it is quantityt contract.
We may have different line items with different cost..
my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
please explain/clarify
regards
subbu

Hi,
The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined based upon the total net value of the entire purchasing document.
Cheers,
HT

Release strategy for Negative Service Entry in ML81N

Similar Messages

Maybe you are looking for