RE:[sap-log-mm] KONP to PIR Number

Posted by ha_tran (Senior SAP Supply Chain Business Analyst)
on May 22 at 8:11 PM
Hi Anindya,

As I said in my previous reply, it is very much subject to how your PIR is maintained that the related record will appear in either A017 or A018.

Cheers,
HT

---------------Original Message---------------
From: stonehenge
Sent: Tuesday, May 17, 2011 12:04 PM
Subject: KONP to PIR Number

How do we extract the PIR Number from KONP condition record number?
Gurus please help

Regards
Anindya

__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
  
ha_tran
SAP Logistics Material Management Top Contributor

Contributed the most posts in a group for 3 consecutive months to earn a Gold Achievement
Popular White Papers

In the Spotlight
Which response to your Toolbox.com Groups post was the most helpful? Use 'Best Answer' to mark highest quality content.
_.____.__

Re: Re: [sap-log-mm] Split Valuation with MRP

Posted by sharadphadke (AGM MATERIALS)
on May 22 at 3:58 PM
Why not open a separate plant for such materials
Sharad

---------------Original Message---------------
From: Duri Gopalakrishna
Sent: Friday, May 20, 2011 11:30 AM
Subject: Split Valuation with MRP

Hi

You can store faulty material in a separate storage location and eliminate
that storage location from MRP by making it non MRP relevant

All the best
Gopalakrishna Duri

__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
  
Popular White Papers

In the Spotlight
Toolbox.com Marketplace: Take online training courses in SAP and other specialized areas of business and IT.
_.____.__

Re: [sap-log-mm] KONP to PIR Number

Posted by stonehenge
on May 22 at 1:10 PM
Nothing appeared on the A017 table.

---------------Original Message---------------
From: talyruger
Sent: Saturday, May 21, 2011 2:39 AM
Subject: KONP to PIR Number

Use Condition Record number as link to get Condition value in KONP from A17
for PIR

__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
  
Popular White Papers

In the Spotlight
Which response to your Toolbox.com Groups post was the most helpful? Use 'Best Answer' to mark highest quality content.
_.____.__

Re: [sap-log-mm] New PO Release codes not getting into effect

Posted by kalyan (MM Consultant)
on May 22 at 1:08 PM
Dear Please tell me the steps for de-activating

Thanks
Kalyan

---------------Original Message---------------
From: morise
Sent: Sunday, May 22, 2011 12:11 PM
Subject: New PO Release codes not getting into effect

Hi u need to diactivate the old characteristics after setting the new release codes and new PO Groups to eliminate conflicts with the old PO settings On Sun May 22nd, 2011 3:57 AM PDT kalyan via sap-log-mm wrote: > > >Dear Guys > >There is already a Release group and Release codes and Release code assigned to the Release groups. Now recently the requirement is one of the Release code description to be changed and also the changes shouldnt affect the Old PO's. So We made a New set of Release groups and Release codes with the New Requirement. But when the PO is made, this New Release groups is not coming into effect, bcos of that old releease code is appearing. Please suggest how to proceed on this, > >Thanks and Regards >Kalyan

__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
  
Popular White Papers

In the Spotlight
Toolbox.com Marketplace: Take online training courses in SAP and other specialized areas of business and IT.
_.____.__

Re: [sap-log-mm] New PO Release codes not getting into effect

Posted by morise (Senior Procurement analyst)
on May 22 at 12:11 PM
Hi u need to diactivate the old characteristics after setting the new release codes and new PO Groups to eliminate conflicts with the old PO settings On Sun May 22nd, 2011 3:57 AM PDT kalyan via sap-log-mm wrote: > > >Dear Guys > >There is already a Release group and Release codes and Release code assigned to the Release groups. Now recently the requirement is one of the Release code description to be changed and also the changes shouldnt affect the Old PO's. So We made a New set of Release groups and Release codes with the New Requirement. But when the PO is made, this New Release groups is not coming into effect, bcos of that old releease code is appearing. Please suggest how to proceed on this, > >Thanks and Regards >Kalyan

---------------Original Message---------------
From: kalyan
Sent: Sunday, May 22, 2011 9:59 AM
Subject: New PO Release codes not getting into effect

Dear Guys

There is already a Release group and Release codes and Release code assigned to the Release groups. Now recently the requirement is one of the Release code description to be changed and also the changes shouldnt affect the Old PO's. So We made a New set of Release groups and Release codes with the New Requirement. But when the PO is made, this New Release groups is not coming into effect, bcos of that old releease code is appearing. Please suggest how to proceed on this,

Thanks and Regards
Kalyan

__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
  
Popular White Papers

In the Spotlight
Toolbox.com Marketplace: Take online training courses in SAP and other specialized areas of business and IT.
_.____.__

[sap-log-mm] New PO Release codes not getting into effect

Posted by kalyan (MM Consultant)
on May 22 at 9:59 AM
Dear Guys

There is already a Release group and Release codes and Release code assigned to the Release groups. Now recently the requirement is one of the Release code description to be changed and also the changes shouldnt affect the Old PO's. So We made a New set of Release groups and Release codes with the New Requirement. But when the PO is made, this New Release groups is not coming into effect, bcos of that old releease code is appearing. Please suggest how to proceed on this,

Thanks and Regards
Kalyan
__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
View this online
  
Popular White Papers

In the Spotlight
Toolbox.com Groups Discussions Support BBCode. Share Code Snippets with Peers
_.____.__

RE:[sap-log-mm] Does anyone have a simple MM01 (replacing) tool available?

Posted by Heather Woytash (Sr SAP Business Systems Analyst)
on May 22 at 9:57 AM
WE created a ZMM01 transaction because the users that are creating the materials don't know the values for many of the fields (and we don't have a process for routing new materials through the areas). There are about 10 choices for type of material, each is tied to a copy from material, which contains all the views that are requitred. The user only enters about 10-12 fields that are different than the copy from (including classification data). It covers about 80-90 % of the materials that are created. We have an "expert user" who creates the exceptions.

---------------Original Message---------------
From: dklerkx
Sent: Tuesday, May 17, 2011 5:57 AM
Subject: Does anyone have a simple MM01 (replacing) tool available?

Customer wants to simplify input for MM01.

__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
  
Popular White Papers

In the Spotlight
SAP Enterprise Mobility Webcast Watch today!
_.____.__