cancel
Showing results for 
Search instead for 
Did you mean: 

about release procedure

Former Member
0 Kudos

hi sap guiders

any body can explain me the procedure of "release Procedure at Item level with using classification"

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

Please go thru the link.You can understand clearly.

http://www.sap123.com/showthread.php?t=59 -Release strategy

Regards

Ramakrishna

Answers (2)

Answers (2)

former_member197616
Active Contributor
0 Kudos

Hi,

Please note that release procedure with classification and without classification are mutuallu exclusive.

Purchase requisitions can be released both at item level and header level.

Release Procedure for Purchase Requisitions

Two different procedures are available for requisitions:

With classification

With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".

Without classification

With this procedure, requisitions can only be released at item level.

Use the path at spromaterials managementpurchasingpurchase requisitionsrelese procedure---release with classification.

Create Class

Create Charectarestic

Create release groups,release codes etc.

Please note that release procedure is globally applicable.

Take the help of a mm guy while crating the release procedure else you may face troubles.

Regards,

Raghu.

Former Member
0 Kudos

"release Procedure at Item level with using classification" is not possible.

With Classification, release strategies are effected at Header level only.

Thanks,

Pankaj

Former Member
0 Kudos

Hi Pankaj,

Please be careful, your comment is misleading.

the Purchase requisition release strategies can be at the line item level, it is only the PO release strategies that are ONLY at the header level *(and even there you can include SOME basic checks on the line item data)

Steve B

Former Member
0 Kudos

Thanks Steve

former_member562193
Participant
0 Kudos

Hi Steve,

Can you please tell what and all basic checks can be done in Release Strategy on line item in PO and how this can be done ?

Regards,

Lucky

Former Member
0 Kudos

Hi Lucky

Sorry for interrupting but this is told many times that Purchasing documents(PO,RFQ, SA and Contracts) can only be released at header level and not possible to release at item level.If you observe there is a basic logic behind this PO is released to Vendor which is a external party and you never wanted to send the same PO multiple times to the vendor as and when item release takes place.

where in case of PR it is a internal document and you can get initimation any number of times as it is not going out of your company.

having said that if still you want to release a PO at item level then you can achieve it in 2 ways but both are not advisable and it is like cheating the system.

1) Suppose you want to release a PO based on material group which is different for each line items(say 5 are there in your PO). now 1 st thing you should this charaterictics defined under release strategy. then in CL24N you should have a value X for material group. now you have to keep in mind that this X should always be there in line item number 1 in the PO as a value for material group. as system will search for 1st line item and if this value matches with CL24N then it will release your po. but still basic purpose will not get solved.

2) In CL24n do not assign any vaue to material group , leave it blank. then also system will allow you to release the PO.

Request you to please check both the cases and let me know the results.

regards

Yogesh

former_member562193
Participant
0 Kudos

Hi Yogesh,

Thanks fo your information, there is another problem came up before I check for this MatGrp in Line Item. When I changed the Characteristic and added MatGrp there, the MatGrp does not appear in Clasification in Release Strategy. I deleted and recreated the Strategy and also unassinged and reassigned the object to class in CL24N, but still the MatGrp does not appear in the Clasification in Rel. Strategy.

Is there any way correcting this ?

Regards,

Lucky

Former Member
0 Kudos

Hi,

the field MATKL is used in the CEKKO structure and can be used in the release strategy.

Did you add it as CEKKO MATKL (which is the correct way) and not EKPO MATKL?

But remember that the basic concept is that POs can only be controlled at the header level and material group is at the line level. This means that it will ONLY read the MATKL of the FIRST line item on the PO.

But we are using line item fields here (Plant) and the material group is also available on CEKKO.

Steve B

former_member562193
Participant
0 Kudos

Hi,

Yes, I have used MATKL in the CEKKO structure in Characteristic and assigned the same Chanracteristic to the respective Class of Release Group. However, still the MatGrp is not appearing in Classification and shows this entry as inconsistent when click on the Incoinsistent button in Classification. Do you know why ?

Can you assist in this ?

Regards,

Lucky

Former Member
0 Kudos

Hi,

It sounds like the characetristic master data is wrong.

check that the staus of the characteristic is "released"

check that you have specified "additional values" on the Values tab (you don't have to specify the material groups individually)

As long as you have used CEKKO and MATKL on the Addnl data tab then all should be well.

Steve B

former_member562193
Participant
0 Kudos

Hi,

I checked the characteristic and it is all ok i.e the status is 'Released' and other field values are also fine. However, when I click the Classification button system gives the message "Error in classification (class PO_RELEASE class type 032)".

As mentioned earlier I have tried deleting and recreating the Rel. Grp , Rel Strategy, but that was of no use.

How can I know what is the Error in classification ?

Regards,

Lucky

Former Member
0 Kudos

Hi,

This message indicates that the problem could be with the Class and not the characteristic, so check the settings of the class PO_RELEASE .

But it is very difficult to know what the cause will be. You really do need to check each and every field on the class and all of the classifications linked to it and eliminate each one by one.

Start with the most recent changes made.

Steve B

former_member562193
Participant
0 Kudos

Hi,

I checked the Class and everything was fine there. However, I removed all the Charactereistics, saved the class and then reassigned all the Characteristics back to the same Class. There was then no error shown in the classification but the MatGrp Characrteristic is still not appearing in Classification.

I added the MatGrp Characteristic later i.e. in the existing Class having other Chatracteristics. Is this the reason of the error because I added the new Characteristic MatGrp in the existing Class ? Can not we add the new Charateristic in the existing Class and existing Release Strategy, at any time later if required ?

Regards,

Lucky

and then also tired Do I need to delete the Class and then recreate it ?

former_member562193
Participant
0 Kudos

Hi,

Can anyone Help on this ???

Regards,

Lucky

Former Member
0 Kudos

Hi Lucky

It should not be a problem adding a new charateristic to the existing one and attching them to a class.i still suggest you to try once more last time though, delete all the characteristics and class. then first create desired characteristic in CT04 and then Class CL01.

Anjan

former_member562193
Participant
0 Kudos

Thanks Anjan. However, I did not want to do that. I wanted to resolve this issue without redoing the whole process.

Regards,

Lucky

Former Member
0 Kudos

Hi

Please refer OSS note: 493900 .Note is on FAQs on Release strategies.Each and every point explained.

If you don't have access please give e-mailid, i will forward the note.

Regards

Ramakrishna

former_member562193
Participant
0 Kudos

Hi

Thanks for the information, however, SAP note 493900 does not describe the issue I have.

Regards,

Lucky

Former Member
0 Kudos

Hi,

I have just tried this myself and it worked without error.

Firstly make sure that you have the correct class (have a look in the release strategy config of the reelease group).

Then create a new characteristic and simply enter the CEKKO and the MATKL on the additional data tab (this will fill in all of the fields on the first tab (basic data) so don't enter anything in these fields go straight to the additional data tab.

Then simply add this characteristic to the existing characteristics on the class and it should work and existing strategies will also have this new characteristic available to use.

Steve B

former_member562193
Participant
0 Kudos

Hi Steve,

I deleted and recreated the Characteristics, Class, Rel. Grp, Rel Codes, Rel. Strategy from scratch. Then it showed the 'MatGrp' Characteristic in the classification. I created the same Characteristics, Class and rest all with same names, sequence and in the same manner as I created earlier, however, it is working now but did not work earlier. Could not understand the root cause of the problem i.e. whether it was in Characteristic, Class or Rel. Strategy ?

I think it creates some inconsistencies if a new Characteristic is added in the existing Class which is alraedy assigned to some Release Strategy ?

Anyways, that issue is resolved now.

Another Related Question:-

You mentioned earlier in your other threads that PO Release Strategy will take in account only the first line item for 'MatGrp' Characteristic. What if there are other line items with different Plants or MatGrps or both. Will Release Strategy ignore the other line items data ?

Regards,

Lucky

Former Member
0 Kudos

Hi,

Adding an additional characteristic to an existing release class should not present any problems, I did exactly that to check what was going wrong and it did not cause any problems.

There really MUST have been one field or settiong somewhere on the class or characteristic that was causing this. But at least now it is working.

As for your additional query, yes it will ignore the other lines on the PO, it could not handle the situation where there are conflicting entries and so it must only read one line.

Steve B