Error In release of Purchase Requisition

Hi All,
In Development Client PR release strategy is working fine but when iam testing in testing client PR release startegy is not working.
I have created class and characteristics before transporting the rel groups but when i checked i am getting error in classification.
What would be the reason? is there anyway we can trasport class and charecteristics.
Regards
Krishna

Hi,
In my understanding the correct way to transport characteristics is using transactions BD91, BD92 and BD93.
BD91
Characteristic                RELEASE_STRAT_CHAR
Logical system               EQ0CLNT100_X
Change number             400000000XXX
Valid from                      31.03.2011
RUN
BD92
Class type                    032
Class                            RELEASE_STRAT_CLASS
Logical system             EQ0CLNT100
Change number            400000000239
Valid from                     31.03.2011
RUN
BD93
Class                            RELEASE_STRAT_CLASS
Class type                    032
Logical system             EQ0CLNT100
Change number            400000000239
Valid from                     31.03.2011
This way you can transport classes and characteristics from each client, don't forget to create the modification number in each client before execute these transactions to transport the classes and characteristics.
You can check tables KSSK and AUSP to have sure about the transport too ^^
See ya
Jony

Similar Messages

Overall release of purchase requisitions - pr document type

hi,
what is the importance of the indicator Overall release of purchase requisitions while defining the PR document type.
Overall release of purchase requisitions
Determines that the items in a purchase requisition are all released at the same time (rather than individually).

Hi Manipal,
overall release makes the release of all the items in the document.
u can also release itemwise in PR only and in all other external documents overall release is only possible
hope it wud have answered ur question.
Reward if useful
Shawn

Plan only releases one purchase requisition at the time

has anyone seen this scenario? When the planner checks multiple purchase requisitions for release and then, when he attempts to release them, the dialog box shows that only one req got released?

That is unusual.
Has the planner saved the earlier records after checking the for release box? Was there any error/warning message?
Have you checked on the Source side if 1 or more reqs. got created?
Is it possible that the other records were Internal reqs or wip jobs?
Sandeep Gandhi

Error in creation of purchase requisition

Hello Sap Guru,
When we are trying to create a purchase requisition under t.code ME51N, we are getting error message "enter valuation price"?
If anyone can please explain the reason & solution of this error.
Thanks In advance
Deepak Garg

{code)When we are trying to create a purchase requisition under t.code ME51N, we are getting error message "enter valuation price"?{code)
Hi,
it is sap standard process when you create PR and if material master record exist the price is automatically taken from the valuation price field. if record not exist enter lum sum price of requested material price.
When purchase guy create po with reference to Pr they can change valuation price also.
In custommization for Purchasing under Purchase Requisition -> Define Screen Layout at Document Level, you can set price and price unit. The Valuation price field can be set as a mandatory or optional input field.

Error when creating a purchase requisition in reference to a contract.

Hello All,
My client have a requirement that , He wants to create a purchase requissition with Item catogery-B and account assignment-K
with reference to a contract.
when we are trying to create a purchase requisition with Item catogery-B and account assignment-K
with reference to a contract the system is throwing an error: "Item categories in agreement and requisition incompatible".
I had searched for the relating documents and tried all the conbinations but could not find the solution.
Could any body help in this regard.
thanks in advance.

Hi Gayathri
I thought so. So that means you are unable to create a contract with the combination of K and B which is why you are not able to adopt it in the PR with the same results.
As far as entering the limit goes, you would be making a value contract in which you would have to enter the value of contract that you need to create for vendor. Also, for the second error, once you have created a contract with the particular account assignment, u cannot change it. You would have to create a new contract with the desired account assignment category and then try creating a PR. Hope this helps!

Error while creating a Purchase Requisition T Code ME52N

Dear Freinds,
The users are trying to create the Purchase Requisition, however the system gives the error message that the GL Account xxxxxx cannot be used, as the comparison of the field selection strings are not comparable with the Account Assignment Category E. Message no. is ME045. How could we resolve this?
Thanks for the help.
Regards

Dear,
check the FSG for the GL Account 200010 and go to TCcode OBC4 and check the status of field 'Asset number / subnumber' and then go to TCode OME9 and select A and check the field status for field 'Asset number / subnumber'. Status at both areas are different hence system is not accpting. Make status identical.
Regards,
Sandip

Enter short text error when creating a purchase requisition using ME51

Hello
I would be grateful if someone can help. I am currently trying to raise a purchase req using ME51. The purchase req is for one item so i enter details of this item on line 1. However when i try to save the purchase req i get an error message stating "enter short text" on line 3 and it does not let me continue. Line 3 however does not contain any item information so i dont understand why i am getting this error message.
Another user created the same purchase req and it worked fine for them so i am not sure why i am getting this message.
I would be grateful if you can please help.
Thank you
Regards
Bindi

Syed
I have tried logging off and logging back in and still having this issue.
Jurgen
No im only having this problem in a ME51 creating purchase requisitions and not in a CATT or any batch input recording
Regards
Bindi

How to find out who has release the purchase requisition?

Hi,
I have a Purchase Requisition Number with me and I want to know who has released it. Can any body please help me how to find this?
Waiting for your valuable responses! Thanks in advance.
Regards
Faisal

Hi,
Thanks for your response. However, is there not any tcode by which we can find it out?
By the way I have done the following to find it. Kindly confirm if I have done it correctly:
1. Executed tcode me23n
2. Menu Purchase Requisition->Other requisition
3. Specified the PR number.
4.Menu Environment -> Item Changes
5. Here in this screen, I got some information saying :
Person responsible (user id), Date, Time, Transaction, Change Doc etc..
Here it says that, one user executed tcode me54 and release indicator is changed to 3.
I think this is only the user who has released it.
Anyway, kindly confirm the same.
Regards,
Faisal

Error in Bapi : Change Purchase Requisition

Dear All,
We have requirement where we need to update the Purchase Requisition Quanity.
For this purpose, I am using Bapi '/AFS/CHANGE_AFS_PR_DATA'.
In this I want to change Sheduled Qty. (AFS Grid Qty.), but I m getting error like
"Line item 0010 : different quantities in item and schedule line". (Sy-subrc = 3)
Can any one help me out with this.
Thanks in advance.
Regards ,
Vishal.

Hi,
Refer:
* BAPI to change the PR details
    CALL FUNCTION 'BAPI_REQUISITION_CHANGE'
      EXPORTING
        number                = v_banfn            "<--PR Number
      TABLES
        requisition_items_old = it_old_detail      "<--pass in old PR details
        requisition_items_new = it_new_detail      "<--pass in new PR details
        return                = it_return_change. "<--return table
*   "read for error message while changing details for PR
    READ TABLE it_return_change INTO wa_return_change WITH KEY type = 'E'.
    IF sy-subrc = 0.
      "check for ERROR
    ENDIF.
Hope this helps you.
Regards,
Tarun

No Release without Purchase Requisition in Process Order(subcon)

Hi All,
We have one requirement :
The creation of purchase requisition happens during the creation of process order which is basically governed by control key.
But in case the creation of purchase requisition didn't happen , because of any issue with master data set up in recipe
or say wrong data .
We DO NOT want , the system should allow the release of that process order.
Is there any standard way to achieve the above requirement.
Thanks in Advance!!!!!!

Hello
You can implement your own logic to check the purchase requisition during the release using BAdI WORKORDER_UPDATE. There is a method specific for checks during the release.
BR
Caetano

Error Message when creating Purchase Requisition

Hello,
We are on SRM 4 version in classic scenario.
We are creating a limit shopping but when he has been approved we got an error from the backend system :
Shopping Cart XXXXX3 (Purch. Requisition XXXXX): ME020 Item category X not allowed with document type XX
the same user has already created a shopping cart on limit with no problem but not on the same plant/cost center/gl account...
Do you have an idea of the error message solution?
Thanks!

Hello,
Check the following settings in ECC system.
1) IMG -> Materials Management -> Purchasing -> Purchase Requisition ->
Define Document Types
Select "EC", (or those related with BBP), then double click on
"Allowed Item Categories".
2) IMG -> Materials Management -> Purchasing -> Purchase Order ->
Define Document Types
Select "EC", (or those related with BBP), then double click on
"Allowed Item Categories".
Also, check if note 140846 is applied.
Kind regards,
Ricardo

How to change data after getting an error in me51n,std purchase requisition

how to make input field editable after getting an error message in ME51N,std purchase requisition
Edited by: SQLFOLLOWER on Nov 18, 2009 1:00 PM

Try this
In user_command form...
LOOP AT IT_DATA.
IF CHECKBOX __MARK EQ 'X'.
write logic wht u want....
ENDIF.
ENDLOOP.

Release code - Purchase requisition - Release Procedure

Hello,
In the purchase requisition release procedure with classification, we are defining release codes say K, P etc.
My doubt is , Is this being defined else where based upon the designatin of the person in the organisation, or else, we are defining here straight away?
Best regards,
K.Kumaran.

HI
You are correct, you need to define the release code there only. There is no other place where it is defined. What you have to ensure is make sure that it is of Two character and not single. Assign the codes against the designation of the person as per your requirement.
Regards

Error TD600 when display Purchase requisition

When I try to display a PR with ME53N, the following error message comes:
Text ID * language * not found
Message no. TD600
Diagnosis
You want to read a text which does not exist in the data base (or update memory).
System response
Reading could not be carried out.
Procedure
You need to create this text:
1. Initialization (module INIT_TEXT)
2. Save (module SAVE_TEXT)
Could anybody help me find the reason?

Hello,
Check the following settings in ECC system.
1) IMG -> Materials Management -> Purchasing -> Purchase Requisition ->
Define Document Types
Select "EC", (or those related with BBP), then double click on
"Allowed Item Categories".
2) IMG -> Materials Management -> Purchasing -> Purchase Order ->
Define Document Types
Select "EC", (or those related with BBP), then double click on
"Allowed Item Categories".
Also, check if note 140846 is applied.
Kind regards,
Ricardo

Can't use Overall Release for Purchase Requisitions

I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
             This procedure is applicable only for Purchase Requisitions.
             Here PR is released Item by Item only.
Release Procedure with classification
            This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
            Item by Item and Header level releases can be configured
            For PR - both item by item and Header level release can be configured
            For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
            1) Total value of PR more than Rs 50,000
               create characteristic as "Release_PR_total_value" in transaction code CT04.
              Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
              Tab -values key in > 50000 INR
              Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
              Tab - Restrictions - class type - 032 - Release strategy
            2) Plant
                 Create characteristic "Release_PR_plant" in transaction code CT04.
                 Tab - Basic data - Data type - CHAR; Number of chars - 4
                 Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
                 Tab - Additional data - Table name CEBAN and Field Name is WERKS.
            3) Purchaisng Group
                 Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                Tab - Basic data - Data Type - char, Number of chars eg. 3
                Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil

Error In release of Purchase Requisition

Similar Messages

Maybe you are looking for