PR release strategy with material group

Hi Experts,
Release strategy for Purchase requisition already configured with characteristics Document type and Total net order Value.
For fulfill new requirement we have created New character with Material group.Our requirement is for Two material groups separate release strategy has to be trigger and remaing other material groups old release strategy has to be trigger.For exple if X and Y are two material groups ,which require seperate release strategy.Other than X and Y material groups requir old release strategy.
all the material groups assigned to character.Blank material group also assigned to the character.In release strategy level in classification view we have assigned two material groups( X and Y ) for separate release strategy and remaining material groups and Blank material group to old release strategy.
   At the time of creation of PR if i give two material groups ( X and Y)for different line items, seperate release strategy is not triggering, where as old release strategy is triggeringIf i create PR with single material group( X) for all line items it is triggering seperae release strategy properly.
   For other material groups (other then X and Y )with different line items it is triggering old release strategy properly.
      Kindly help me to resolve the problem.

Hi,
Please add Blank material group to the new release strategy also.
Maruthi

Similar Messages

PR release strategy for material group

Hi,
I have 2 different line items in PR with 2 different mat groups. How can I set up a release strategy for this scenario. Ex-line No 1 has mat group X and line item 2 has mat group Y. Do I release at header level or item wise release is possible

Hello
In PR you can set up this release strategy without classification release strategy.
w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
Laxman

Creating Roles for Purchase Req. release strategy with classification

Hi friends,
Since I have created Purchase req rel strategy where I have four release strategy
1. For Plant 1 When value <= 5000 (Officer) will release , release code 01 release release strategy r1 and rel code L1
2 For Plant 1 When value >= 5000 (Manager) will release , release code 01 release release strategy r2and rel code L2
Now the manager will have 2 release code,if officer is absent he could release the requisition.
Same has to be done for plant 2
The release Group and code needs to be assigned to the Roles , could anybody tell me where i could know about roles and will be able to create roles and assign authorisation objects to the Roles , and release group and code to the enduser.
though its a basis job , since I have no idea , I mean I have never worked with Roles ,as now I have created the Release strategy with classification I need to assign authorisation objects to the Roles as I have four release strategy
1. For Plant 1 lower value of requisition 1 codeL1(Officer)
2 For higher value of requisition 2 code say Li and L2(Manager)
Manager should have 2 codes if officer is absent he could release
Same has to be done for Plant 2
Thanks N Regards
Siddhartha

Hii,
Steps:
1) Create a Role
2) Add the authorization Object M_EINK_FRG by taking the manual option
3) Assign Release Code and Release Grp
4) Assign the Role to the User ID which has the authorization of the Release Code and Grp.
Regards,
Kumar

PR overall release strategy with acc. assignment category characteristics

Hi,
Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
see below more details :
I have created the following PR release strategy with classification.
PR type concerned " NB": overall release
Rlease group concerned : overall release
In this release group i have 1 class
in this class i have 2 characteristics : PR type and Account assignement category.
Release strategy 1 :
PR type = NB
Acc. assignment cat = P, W
Release strategy 2:
PR type = NB
Acc. assignment cat = K, V
TEST 1 : PR type NB, 1 item with P category
OK the release strategy 1 is generated
TEST 2 : PR type NB, 1 item with W category
OK the release strategy 1 is generated
TEST 3 : PR type NB, 2 items with P category
OK the release strategy 1 is generated
TEST 4 : PR type NB, 2 items with P and W category
TEST KO, no release strategy is generated
=> what should i do to solve this issue ?
Thank you in advance for your quick answers,
Isabelle

What is the specific requirement for Overall release strategy?
Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
Every line item generates a PO, so logically should be set to a release strategy.
Bottomline is use release strategy at line item level Unless a specific reason exists.
Regards,
Sameer

Release Strategy with Workflow for PR & PO

Hi Experts,
I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
So User should get the information about the releases for PR & PO.
But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
Points will be awarded .
thanks & rgds
Swamy

Hi Swamy,
The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
How to configure?
Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
Maintain the details u already have in hand:
For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO. After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
Hope this will give you an idea how the workflow works and how to configure it.
Rgds.

PR release strategy with classification

As part of a rollout, we are migrating an instance of SAP to the template SAP. Both the SAP instances are following u2018PR release strategy with classificationu2019.
The limitation is that I can configure only two release group in PR release strategy with classification. One for overall release and one at item level release. Also, I cannot assign two different release class for the same release group. If I add additional characteristics in the existing class and keep other irrelevant characteristics as blank the release strategy doesnu2019t works. the release strategy does not triggers.
Any pointers to solve this will be highly appreciated.

Hi Ashish,
If your requirement is to have release strategy with more or different characteristics than in the existing system,you may create a new release group and assign the same to release class.There no restriction for having multiple release groups for same release class.Then create new release strategies for the newly created release group and so on.
Regards,
Edited by: Dayanandan Kamath on Oct 20, 2010 7:52 AM

Material replication from R/3 to SRM - Issue with Material group

Hello All,
                  I am working on BADI PRODUCT_CUSTOMER2 and method MAP_R3_TO_CRM_MATERIALMaterial replication part from R/3 to SRM.
I am using a Ztable to map r/3 material group to SRM material group(Product category).
For example Material M1 with material group 100 is transferred to SRM. Material group(Product category) 100 exist in SRM, but I am changing the material group to 200 in the product_customer2 badi. its working fine.
In another scenario, Material with material M1 with material group 300. Material group(product category) 300 does not exist in SRM,
I am changing the material group to 200 in the bdoc, in the product_customer2 badi. It is not working. The LUW is failing in SMQ2 transaction with the error "Error in Mapping (Details: transaction SMW01)". The BDOC is failing with error "Category for material group 300 does not exist"
I tried to deactivate the badi PRODUCT_CUSTOMER2, even then the FM MAP_BAPIMTCS_AND_PROCESS is validating the material group from R/3.
I tried to change the material group 300 to the existing material group 200 at initial stage in debugging in function module MAP_BAPIMTCS_AND_PROCESS but still the bdoc is failing with error "No storage form defined for product type 01 / logical system".
I am doing my testing using the following steps.
1. change the material descriptioni in MM02 in R/3.
2. An item is displayed in the queue in SMQ2 in SRM.
3. I have debugged the LUW and analyzed my badi by setting breakpoint at method MAP_R3_TO_CRM_MATERIAL, its changing the material group in the bdoc properly.
   that didnt work.
   also i tried to change the material group in the function module MAP_BAPIMTCS_AND_PROCESS before the badi is called.
4. I am checking the BDOc status using tcode SMW01 and checking the material using tcode COMMPR01.
can someone tell me how I can change the R/3 material group to SRM material group at the time of mapping in SRM?
Thanks
Sathish PM

Hi find below for the product cat
Steps to create the product category in SRM:
1) Create MM material groups in ECC client. This will create a transport. Go to SRM Tcode R3AS and select the object u201CDNL_CUST_PROD1u201D from the list and run it. You can monitor the job using R3AM1 in SRM. This will bring the material group into SRM. This can be seen in TCode u201CCOMM_HIERARCHYu201D in SRM.
2) Once it is done. Go to IMG in SRM and go to path SRM> SRM server> Cross app biz settings> Account aassigmnet> Define GL code for Acc *** Cat and Prod Cat. Maintain the GL code against this prod cat for all the account assignment codes. This is client specific setting and need to be done in every client by opening it. This GL code is given in the form in ticket.
3) Do a test and check if the product category is available for procurement in SC.
Regards,
Satish

Assignment of GL Accounts with Material Groups

Hi Gurus,
Please tell me how can we assign GL accounts with material groups and what are the different options in this assignment.
Please revert asap.
Thank You

Hi,
In IMG settings
SPRO MMPurchasing --Material master --Entry Aids for Items Without a Material Master
Here with respect to your material group you will assign the Valuation classes.
For this valuation classed in OBYC settings you need to assign the G/L accounts for the Transaction key "GBB" or etc which ever you want.
take a help of FI consultant for this assignment in OBYC
rgds
gsc

Tranposrt - Purchase Requisition Release Strategy with Classification

Gurus!
Tell me if I want to Transport the Purchase Requisition release strategy with classification. The Data in each charisteristics in each PR Strategy that I have set in Dev is not getting transported to Quality.
Do I have to enter the data in characteristics again in Quality and the same procedure I have to apply for Production.
If yes, in this scenario, Can I make Production modifiable.
Regards
Sajid

Hello,
Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
Cheers !

MM Release Strategy with Cost Centre

My characteristics for the release strategy is Accnt Assigmnt (KNTTP), Cost Centre (KOSTL) and Amount (GSWRT). I link all to the ceban straucture, and for the cost centre, I entered in the value tab the cost centres that I am using, and I entered the cost centres in the release strategy. Everything seem OK for the release strategy, but the release strategy is only selecting the strategy according to the values and not considering the cost centre, what can I do let it consider the cost centre and the value. I have been struggleing with this problem more than a week now. I tried everything that I can think of. Can someone assit me in this matter. I am on ECC 6.
Thank you.

Refer OSS Note :: 52225
Solution ::
Summary
Symptom
Purchase requisition release strategy with classification does not work as expected when the characteristic for cost center KOSTL is included.
Message ME297 is displayed.
Additional key words
CEBAN-KOSTL, KOSTL, Cost center, Release strategy, OMGQ, ME297
ME51, ME52, ME53
Cause and prerequisites
Numeric values used for the cost center characteristic in the purchase requisition release strategy with classification is not recognized. CEBAN-KOSTL is a CHAR field of length 10.
Solution
Enter leading zeros for the cost center value in the release strategy. eg. If the cost center value is 123456, while entering this value for the cost center in the release strategy, enter it as 0000123456.
Cheers !!!!!!
Biswajit

Release Strategy With Classification

Hey All,
I would like to get some information about release strategy with classification for purchase requisation and purchase order.
Please send me some information regarding this.
Thanks
Kawal

hi,
To see the all the linkages firstly see the classifcation and class defined in the sap system at:
SAP easy access --> Cross application components --> classification system --> master data --> characteristics and classes(CT04 and CL02)...
TO see the customisation, check:
Spro --> MM --> Purchasing --> PO/PR etc --> Release procedure --> Rel procedure with classification --> Here check for all the different transactions...like Relase codes, release stategy, access sequence, schema etc...
Also one important point abt it is:
PR is possible to release at header as well as at item level...
But PO and other external docs are only possible to release at header level only...
In the customisation check all the linkages you will get best out of it....
Regards
Priyanka.P

Searching for material with material group

Hi Friends,
How to get the old material no. material no., description after searching for material with material group.please reply....

SE16
table MARA
field BISMT is the old number
MATKL is material group
table MAKT
MAKTX description
you can make a query join with MATNR
Best Regards

GRN with material group

Hi,
The PO cretaed with material group ( non coded materail)
We have some material( non coded materail) received from Manufacturer for which we don't want to take Cenvat Credit. So, What option we need to select in GRN Excise Tab? We have maintained conditions of Excise credit in PO. And material is non-coded. So, where will Excise value will go in MIRO transaction.
while doing Goods reciept, in Excise invoce tab both header & item level what values need to be enter like ( material type: Asset, Non Cenvatable etc..)
Please inform the overall procedure for it.
regards,
Obulesu

Hi,
Excise value is dependent on chapter id, so for no coded material, excise tab will never come during gr.

Purchase order release strategy with multiple characteristics

Hi All,
We have Purchase order release strategy based on the following characteristics:
Total Net Order Value
Purchasing Organization
Release strategy Type
a few other custom fields
We would like to have PO's with release strategy based on a particular Material Group [say X]. I have created a new Characteristic with respect to CEKKO-MATKL and added this characteristic to the same class.
I have created a new release code [HR] [we need a different person to sign off] and a new release strategy [TR] for which I have assigned the release code HR. In this release strategy, I have set it to get activated for a particular Material Group that does seem to work, but the remaining PO's are not getting triggered for other material groups. For other release strategies, I have left the material group field blank, because they need to be triggered for any material groups except X.
Could you please let me know if I am missing something or is there an alternate approach to this ?
Thank you,
Satish

Hi,
Obviously system will not trigger release strategy in ur case since in the classification data for other strategies u have left it blank excepting X for one strategy.
Since u have added a new characteristic Material group and assigned it to class then system expects an input for Material group for triggering release tab.If this is left blank then system by default will not trigger release strategy tab.
Solution:
First add all existing material groups in values tab of mat group characteristic then maintain the required set of material groups except X in other strategies in classification data.
Hope this is clear to you.
Regards,
Uzair

Issue: Purchase order release strategy with storage loaction.

Hi Friends,
I have created release strategy for purchase order considering following characteristics.
1. Plant
2. Purchase organization
3. Purchase group
4. Document type
Hence the release strategy is working fine.
Now the requirement is changed, PO approves should be picked depending on the storage location wise. So i tried to create characteristic for storage location with table name CEKKO and with field LGORT. However system not allowing to create, telling that field LGORT not found in table CEKKO.
Can any one tell me how to maintain this LGORT filed in structure CEKKO.
Thanks in advance
Shashidhar

HI Shashi ,
Thanks for your quick response,
I have Appended a structure to Standard Structure CEKKO with Field LGOBE.
Also we written the code :move: i_cekko = e_cekko, in user User-Exit M06E0004 function exit
FUNCTION EXIT_SAPLEBND_002.
However, the release strategy is not triggering when PO is saved,
also the user-exit is not getting triggered , even though i have included the statement ' Break-Point'
in it.
Kindly reply.
Thanks ,
Shashidhar

PR release strategy with material group

Similar Messages

Maybe you are looking for