cancel
Showing results for 
Search instead for 
Did you mean: 

Release not triggering for standard PO?

mutharasu
Explorer
0 Kudos

Hi,

I have configured my standard Po document type (NB) for automatic Po a few days ago. The PO generated but release is not triggering, tried manually creating Po using the same document type but still release not triggered. Yes i have assigned Strategy and checked the characteristics (CT04) all seems to be OK. All my other custom PO documents which were created earlier were checked and release are working fine as they are supposed to be.

Thanks in Advance,

Bharath

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

Could you please provide screenshot of the characteristics and class from your live / production system.

Also kind of create a screenshot of the purchase order being created, while creating the PO, just before saving the PO do the checking of the PO i.e. Ctrl+Shift+F3, does any messages show in the message bar stating "releases will be effected".

Moreover do provide the configuration screenshot of the characteristics and class created

mutharasu
Explorer
0 Kudos

The Po which did not trigger the release, tries using ctrl+shift+F3 nothing shows up. capture11.jpg

Screen shot attached of classes and characteristics

capture1.jpg

0 Kudos

Hi,

Sorry for the delay. Could you please share the screenshot of the following

a. Characteristics Details for all (Basic , values, Additional Data, Restrictions if any)

b. Check whether all the values are maintained for the individual characteristics at Classification in the Release Strategy

c. Also check the "Check Release Strategy" for any inconsistency.

0 Kudos

Hope when you are using check options for other POs, the release strategy is being triggered

mutharasu
Explorer
0 Kudos

sorry for the delay,

i have attached the details.

mutharasu
Explorer
mutharasu
Explorer
mutharasu
Explorer
0 Kudos

Dear IT Support,

I know this would be really stupid but could you please share the screenshots of the Basic data and Addnl data for each of the characteristics. I am really intrigued now observing that most of things which i have mentioned was in correct order. Check if the characteristics are all in released state. i just wanted to be sure if i am missing any particulars.

0 Kudos

Dear IT Support,

requesting you to share the details of Basic data of the Class too. Also this is very silly but i hope all the characteristics and class are configured correctly in the production system from which you sharing the screenshots. Correct!!?, waiting for your reply!!

mutharasu
Explorer
0 Kudos

Hi Sayan Paul,

Sorry for the delay. Currently i have have created a customized PO document and assigned it to Automatic Po which is working fine. But i to need to know why it is not working for standard Po. I have been sharing you the screen of the quality server which runs on a month old production backup. capture1.jpgcapture2.jpg

mutharasu
Explorer
mutharasu
Explorer
mutharasu
Explorer
0 Kudos

Why is the Purchasing Organization doesn't have any Field and also you haven't shared any screenshot of the netvaluem,companty code and release version!!, are these screenshots taken from Production system, If taken from quality ensure that all the values are in sync with the production so that we are able to locate the root cause easily.

mutharasu
Explorer
0 Kudos

sorry for the delay

The purchasing organization field is blank in my production server and yes my quality is in sync with production, but i had filled the fields in my quality and tried testing but still no results.

sorry i didn't understand what you mean by release version.

mutharasu
Explorer
mutharasu
Explorer
0 Kudos

In your Class you have mentioned a characteristics as release version.. I was talking about that, but still i am unable to find any discrepancy in the shared screenshots.

mutharasu
Explorer
0 Kudos

Thanks for trying.

BijayKumarBarik
Active Contributor
0 Kudos

Again check other release parameters as you have one PO document type as release parameter...

Check for which company code( as this one a release parameter) you are creating PO with NB and that company code value available must be in your release strategy.

BijayKumarBarik
Active Contributor
0 Kudos

Just cross check PO document type value NB available in your PO release strategy with release class and release group in CL24N and if not -assign it in CL20N. Now cross check by creating a new PO!

mutharasu
Explorer
0 Kudos

capture.jpgHi

I had checked the release group and release class and again created a Po still does not trigger, i tried adding or changing the order type (NB) in strategy which is working for other document types. strategy is not triggering only for NB order type(standard PO). Please refer attachment.

NTeunckens
Active Contributor
0 Kudos

Please see the SAP-KBA on Release Strategy in MM-Purchasing, such as :

  • SAP-KBA 2445131 : Expert Webinar Rel.Strategy Purchasing Documents
  • SAP-KBA 365604 : FAQ Release Strategies Purchasing
  • SAP-KBA 493900 : FAQ Release Strategy
  • ..


Hope this helps

Nic T.