Perform check after release step of purchasing requisition
Hi,
does anybody have a suggestion where to place best some logic which needs to be performed after a release step is performed successfully.
background: we use different types of Purchase requisitions, while each one is assigned to a static release strategy. I like to change it in more dynamic way by adding certain logic after a release step is performed.
example: if preceeding release step was 10 and purchase requisition is of type x then check purchase value and account assignment in order to process the current stepo automatically.
Currently the logic runs during a nightly job, but I would like to add it immediately after a release has been performed. I would imagin something like user exit, BusinessAddIn, or an event which I can use assign the job.
Can anybody suggest something?
Thanks in advance
Best regards
Torsten
Edited by: Torsten Hübsch on Apr 29, 2011 10:36 PM
Hi,
Enhancement M06B0005 is relevant for PR in case of overall release
Check on trx SMOD :
Enhancement M06B0005
Short text Changes to comm. structure for overall release of requisistion
--> Function module Short Text
EXIT_SAPLEBND_004 Changes to Communication Structure for Over.
Enhancement M06B0002 is for item-release
Short text Changes to comm. structure for purchase requisition release
-->
Function module
EXIT_SAPLEBND_001
BR
Nadia Orlandi
Similar Messages
-
Release Procedure of Purchase Requisition
We are trying to configure the release strategy of purchase requisition with classification system. Following field are included in the release strategy: document type, creation indicator, requisitioner, item category, purchasing organization and total value of item; but the strategy is not effecting due to the item category field. We have verified all the remaining fields and they are working properly.
Following are the characteristics detail of the item category.
1.Multiple values checked in the Basic Data tab
2.Following values set in the Value tab
a. blank for standard
b. K for consignment
c. D for services
3.Following values set in the Additional data tab
a.CEBAN in the table name
b.EPSTP in the field name
However, we have also verified the following table and field values in Additional data tab
1. CEBAN table with PSTYP field
2. MEREQ3211GRID table with EPSTP field
3. MEREQ3211GRID_DATA table with EPSTP field
4. MEREQ3211GRID_DATA table with PSTYP field
But none of the above is working.
It will be highly appreciated if you provide help to configure the Release Strategy of Purchase Requistion with item category.
Thanks & Best Regards
M. Rehan QureshiHi Muhammad
The item category applied in PR is external one (Field: EPSTP)
In IMG ("Define external representation of Item categories"), a corresponding internal item cat are defined (Field: PSTYP).
In the comm structure CEBAN, the available field is internal item cat. is PSTYP.
Hence u need to maintain the values of internal item cat for the characterisic.
By this, you will get the desired.
warm regards
sairam akundi -
Cancellation of Release of a purchase requisition
Hi,
Currently the system allow to cancel the Release of a purchase requisition eventhought the Purchase Order already created for it.
I could not locate the any system message that actually control this.
How to disallow the cancellation of Release of a purchase requisition if the processing status is 'PO Created'.
Best regards,Dear Eric,
We cant do cancel of PR onece PO created.not only that onece release of PR we cant cancel the PR we can do only flag the release PR.
Hope this will helps you
Prem. -
Wrong Release date in Purchase requisition wh later than requisition date
Hi,
Purchase requisition created through Planned order then Source (contract) is assinged through Transaction ME57.
After that in display of PR as found below mentioned below,
Release date is 27.11.2008 and Requisition date is 04.12.2008. MRP type maintained in Material is Auto Reorder point.
Checked In display changes of PR as Planned delivery time new value is 45 (45 maintained in Contract and contract assigned in source list) and old value is 0 (Material master-MRP 2 view) on 04.12.2008.
My question is How come PR release date as past as 27.11.2008 when requisition (PR creation date) date is 04.12.2008. Suggest any setting required to check.
Looking forward to your expeditious response.
Regards,
C. Sundar RajanHi,
If I guess, there is an exception message "06" on the PR.
check with MDO4, if there is the exception message 06 that means :
In order to get material at requested time you have to release the PR in the past. This message help the purchaser to detect the problem and try to reduce to lead time by calling the supplier.
PR release date = Requested date - safety time- lead time - setup time - processign time- ....
If you want to change the system behaviour you have to change to chage the item strategy ont the:
MRP3/Planning/Strategy group.
best regards -
Release strategy for purchase requisition does not kick in
Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima. -
Rejection(release refused) of Purchase requisition?
Hi all,
Sorry to post again.
In ECC 6.0 i have to reject a Purchase Requisition in the transaction ME54N.
When i am rejecting a PR in ME54N an event in Business object type BUS2105 called 'Rejection_start' is getting triggered. There are two more event in this business object 'Rejected' and 'Rejected_stop'. This is the root cause of my doubt.
Will PR be rejected by just pressing the Reject button in the transaction ME54N or there is some more to be done.
Regards,
Gautham PHi,
Just click on the reject button and save the PR, then the PR gets rejected.
As you are asking about the bussiness object BUS2105 and the events in the business object the details are as follows:
Rejected' : This event is triggered when you are pressing the reject button and save the PR
'Rejected_stop' : This event is triggered when you are cancelling the rejection ( You are approving the PR by pressing release button) after rejection of PR.
Regards,
sampath -
Overall release strategy in purchase requisition
hi,
how do i configure overall release in case of purchase requisition. i have done item wise release in PR. but in case of overall release what field I should take in characteristics? is their required two seperate classes for item and overall release? i've allready chosen the field BSART and GSWRT for item wise release,
plz help me in details
regards
AniruddhaHi
For PRs, there are two types of release procedures available
With classification
With this we can release the PRs both items wise and in their entirety
Without classification
With this we can release only at item level
When you create the Release Group under the release procedure with classification
you check the box " ov Rel P Req (Overall release of purchase requisitions
This Determines that the items in a purchase requisition are all released at
the same time (rather than individually).
This should help to relsove your problem.
Regards
Vikrant -
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
ManuelHi,
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 -
Delivery Date getting Copied to Release Date in Purchase Requisition
Hello,
When i am releasing the Purchase Requsition, what ever the Delivery Date the system is proposing based on the Planned Delivery Days given in Material Master is copied to the Purchase Requisition Release Date.
Is there any error in Customization ??
Regards,
KumarHello Shakthi,
System is considering Delivery date as Release Date when you create the purchase requisition.
Thanx & Regards,
Kumar -
Release strategies for purchase requisitions
Hello,
I'm having trouble with profiles and roles for release strategies, this is the scenario:
-for purchase requisitions we have two approval levels, release code S1 and S2. When release code S1 is cleared, then S2 must be approved. The head of a certain purchasing group will use S1 to approve the requisitions from his own department, and then the financial director will approve with S2. However, finance is also a purchasing group, so in some instances the finance director will have to approve with S1 and then S2.
My question is: how can we use profiles and roles so that the finance director has access with S2 to all (*) purchasing groups, but with S1 for only a certain purchasing group (in this case "500")? we can't seem to be able to define certain purchasing groups to different release codes, purchasing groups must be defined at purchsing requisitiom level.
Many thanks
DanielHI,
Not necessarily, you just need a different strategy for each different combination of release codes involved.
So if certain P groups need to be put through a different sequence of approvals, then have one new strategy for this group of P groups and one for the other combination of P groups.
Or however many different variations you have.
Steve B -
Dear colleagues,
Is any posilble check or test (benchmark) of DB performance before and after CPU patching?
Any testing SAP or SQL report, which makes a load on DB?
Thank you for advice.
Best Regards
Jakub Vaněk> Is any posilble check or test (benchmark) of DB performance before and after CPU patching?
> Any testing SAP or SQL report, which makes a load on DB?
Those test would be synthetic and may or may not reflect your current environment.
I'd check some long running reports in your environment if you see any difference.
Markus -
Release Statergy in Purchase Requisition
Hi,
My requirement is to change the Release codes dynamically.
For eg: As per the configuration there are 6 Release codes 01, 02, 03, 04, 05, 06 according to few conditions then of release codes should change i.e. for one condition 02 03 and 04 for other 01 02 03 and 04 etc.
Is this possible by any enhancement.
Regards,
Ramu N.Hi Vinod,
Please find hte STEP-BY-STEP guide to Pr release strategy
http://sapdocs.info/wp-content/uploads/2009/07/Step-by-step-guide-of-SAP-PR-Release-Strategy-configuration-a-case-study.pdf
Regards,
SuryaD. -
Release Procedure for Purchase Requisitions
HI
i have making a class in cl01 then create Release Groups & link to class but when i save a group massage here Please check release classes (see long text) can anybody help me
thanks vijaypls check the following:
http://www.sap123.com/showthread.php?t=59
regards,
indranil -
Classic Scenario PO after Bidding of ECC Purchase Requisition - PR
Dear SRM experts
Is it possible to create bidding invitation for a ECC-MM-PR and then create a Purchase Order for Winner Bid in Classic Scenario of SRM.
What configuration should be done for making Bid and then PO in SRM in classic scenario to process the MM PR.
AhmedHello,
Transfer of ECC PReq for bidding & creation of ECC PO as follow on document is possible.
See the details - Business scenario - Plan driven procurement.
http://help.sap.com/saphelp_srm70/helpdata/EN/48/3003eb2c8a72d0e10000000a42189c/frameset.htm
Configuration need to be done on SRM as well as on R/3.
On ECC side:
a.Create a Profile: " V_T160PR"
Profile + Syst Log of SRM
b. Create a Filter:"V_T160EX"
Product Category + Purchasing Group + Profile
( PReq satisfying the Pcat & Pgrp combination will be transferred)
On SRM side:
You need to maintain a sperate Local Porg /Pgrp entry in the Org structure for trasnfer of PR's from R/3 to SRM.Under these Org/Grp ,you need to assign the RFC user and this user will be used to create the SC in SRM for the corresponding PR in R/3.
Then, you will run the program BBP_EXTREQ_TRANSFER in R/3 to transfer the PR to SRM sourcing cockpit. Using the requirement created in SRM, buyer can create a bid & as a further follow on document as Classic.
Hope this helps.
Thanks
Ashutosh -
Hi,
Could anybody help me out with the configuration settings of purchase requisition Release.
Client want to set release status for Purchase Requisition , where two persons will be responsible to release the requisition . when the first person releases the requisition , it will come to the second or final person for release ,when he releases then the requisition is released for purchase orders.
Could anybody help me out with the configuration settings.
Thanks N Regards,
SiddharthaUse this steps. below is for PO same do it with PR. that is in place of PO take it as PR.
Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1 Creation of Characteristics
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Characteristic
Transaction Code CT04
2. On the Characteristic screen, make the following entries.
3. In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name Description User action and values Note
Select Addnl Data tab
Table Name Table Name CEKKO
Field Name Field Name GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description Description Total net order value
Status Status Released
Data Type Data type Currency format Selected by system
Number of characters Number of characters 15
Decimal places Decimal places 2
Currency Currency INR
Interval vals allowed Interval values allowed Check this tick box
Multiple Values Multiple values allowed Select this radio button
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2 Creation of Class
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Class
Transaction Code CL02
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Class PORELPROC
Class Type Class Type 032
Choose Create icon or white paper icon to create new class.
Description Description Purchase Order Release Procedure
Status Status Released
Choose Char. Tab to input characteristic name.
Characteristic Characteristic POVAL Created in above step
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3 Configuration of Release Procedure
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Define Release Procedure for Purchase Orders
Transaction Code SPRO
2. On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Rel. Group Release Group 02
Class Class Name PORELPROC Created in above step
Description Description PO Release Procedure
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the entries.
6. Choose yellow arrow to go back to popup screen.
7. Choose Release Codes to select.
8. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Grp Release group 02 Created in above step
Code Release Code 01
Workflow Workflow Leave it blank
Description Description Purchase Officer
Grp Release group 02 Created in above step
Code Release Code 02
Workflow Workflow Leave it blank
Description Description Materials Manager
9. Choose Enter to complete the entries
10. Choose Save icon or Ctrl + S to save the entries.
11. Choose yellow arrow to go back to popup screen.
12. Choose Release indicator to select.
13. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Release ind. Release Indicator 1
Released Released Leave it blank
Chgable Changeability 4
Value change % Change of value 10%
Description Description Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind. Release Indicator 2
Released Released Select Check box
Changeable Changeability 6
Description Description Purchase Order Released
14. Choose Enter to complete the entries
15. Choose Save icon or Ctrl + S to save the entries.
16. Choose yellow arrow to go back to popup screen.
17. Choose Release Strategies to select.
18. Choose New Entries icon and make the following entries:
19. System will give new screen New Entries: Details of Added Entries
Field name Description User action and values Note
Release Group Release group 02
Rel. Stategy Release Strategy S1
Capital Items Release
Release Code Release Code 1 01
Release Code Release Code 2 02
20. Choose Enter to complete the entries.
21. Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22. Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23. Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24. Choose Next Screen icon or choose F8 to continue.
25. If you want to simulate the release procedure you can choose Release Simulation icon.
26. Choose Enter to complete the entries.
27. To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4 Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Cross-Application Components Classification System Assignments Assign Object to Classes
Transaction Code CL20N
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Type Class Type 032
Choose Enter to Assign values.
Release group Release Group 02
Rel. Strategy Release strategy S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Regards
S
Maybe you are looking for
-
How to get SAP application language only with SQL code
Hi all, is there a way to get the current language only whith a sql query on the Database? I know that Ican find that information from the Application object of the UI Api but in this case i can't access them. Thanks in advance, Luca.
-
How do I live preview a Ruby on Rails/Ember application?
I have a Ruby on Rails application and I am under the impression that Edge Code will work with locally hosted web servers to use live preview. I have set up the project settings to use the locally hosted address: http://localhost:3000/ ... However wh
-
Web Gallery duplicating photos
I seem to have a consistent problem of photo duplicating themselves when I add new photos to a Web Gallery. The duplications don't show up on the actual Web gallery but are present within iPhoto, for example iPhoto says there are 96 images and the We
-
Hi i have a doubt in jsp...first i don know much abt jsp so iam gonna trying out a project on supermarket system.Here i have three tables Items,Bill and Report.Iam using three resultset continuously and i have error saying no resultset found.I have s
-
JVM 1.4 seg faults with pure java code?
Has anybody else seen JVM 1.4 seg fault when running pure java code? This seems like it shouldn't be possible, but I get the following at indeterminate times. Unfortunately, it is difficult to isolate since decreasing the size of the program avoids t