Skip to Content
0

PO relelease strategy is not triggering

Oct 26, 2016 at 05:42 AM

243

avatar image
Former Member

Hi,

we have added new field order reason EKPO-BSGRU as new characteristic , created new characteristic and assigned the table cekko , field USRC1 and maintained values ,assigned the characteristic in the class , developer added logic in the exit

EXIT_SAPLEBND_002and include ZXM06U22

SPAN { font-family: "Courier New"; font-size: 10pt; color: #000000; background: #FFFFFF; } .L0S31 { font-style: italic; color: #808080; } .L0S52 { color: #0000FF; } .L0S55 { color: #800080; }

DATA:ls_ekpo TYPE ekpo.
*DATA:lv_bsgru TYPE string.
*
*DATA: lv_exit_name TYPE zpil_exit_id,
* lr_data TYPE REF TO data,
* lr_struc TYPE REF TO data.
*
*FIELD-SYMBOLS: <lt_data> TYPE ANY TABLE,
* <ls_struc> TYPE any,
* <ls_temp> TYPE any.
*
*LOOP AT it_bekpo INTO ls_ekpo .
* lv_bsgru = ls_ekpo-bsgru.
*
* CALL METHOD zcl_pil_execute=>get_set_data_struct
* EXPORTING
* iv_id = 'MM-REASONSFORORDERING'
* iv_input = lv_bsgru
* IMPORTING
* ev_data = lr_data.
*
*
* ASSIGN lr_data->* TO <lt_data>.
*
* ASSIGN lr_data->* TO <lt_data>.
* LOOP AT <lt_data> ASSIGNING <ls_struc>.
* ASSIGN COMPONENT 'USRC1' OF STRUCTURE <ls_struc> TO <ls_temp>.
* IF sy-subrc = 0.
* IF <ls_temp> = lv_bsgru.
* e_cekko-usrc1 = ls_ekpo-bsgru.
* EXIT.
* ELSE.
* CLEAR ls_ekpo.
* ENDIF.
* ENDIF.
* ENDLOOP.
*
*ENDLOOP.
*UNASSIGN:<ls_struc>,<ls_temp>.
*DATA: : lo_badi TYPE REF TO zbdf_mapping_reason_code.
*GET BADI lo_badi.
*
**.Call BADI
*CALL BADI lo_badi->zif_mapping_reason_code~mapping_reason
* EXPORTING
* is_cekko = ls_ekpo
* IMPORTING
* es_cekko = ls_cekko.

but the release is nto triggering in the PO , pls advise

10 |10000 characters needed characters left characters exceeded
Former Member

I am not sure about your requirement!

Can you share requirement details?

If required- You should creates new release characteristics CEKKO-USRC1 and with development you need pass value from your wanted new field to turn around.

0
Former Member
Former Member

with the development in the exit , the value of BSGRU is taking into USRC1 of the structure CEKKO, But release tab is not appearing in the PO header , we debugged the exit , but after assigning the value ( as mentioned above) it is coming out to PO creation screen without release tab in the header , pls advise

0
Former Member

with the development in the exit , the value of BSGRU is taking into USRC1 of the structure CEKKO, But release tab is not appearing in the PO header , we debugged the exit , but after assigning the value ( as mentioned above) it is coming out to PO creation screen without release tab in the header , pls advise.

0
Show more comments
* Please Login or Register to Answer, Follow or Comment.

3 Answers

avatar image
Former Member Oct 31, 2016 at 05:27 AM
-3

Involve Technical consultant and find the route cause of how release tab disappearing!

Share
10 |10000 characters needed characters left characters exceeded
Ajit Kumar Oct 26, 2016 at 07:19 AM
0

Did you check whether USRC1 field is taking the value from BSGRU in debug mode.

Also ensure that the Char values in release strategy is exactly similar to the entries in TBSG table

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

in debug , it is taking the value of BSGRU to CEKKO-USRC1 , but the release tab is not triggering in the PO , can you please advise what are the things missed , we maintained new characteristic and assign the table cekko , field USRC1 and developer added as I mentioned in the question.

0
Former Member

with the development in the exit , the value of BSGRU is taking into USRC1 of the structure CEKKO, But release tab is not appearing in the PO header , we debugged the exit , but after assigning the value ( as mentioned above) it is coming out to PO creation screen without release tab in the header , pls advise

0
Jürgen L Oct 31, 2016 at 12:12 PM
0

Is USRC1 the only characteristic in your release strategy or do you have other characteristics too?

Please show your setup of the classification for your release strategy and show that all other values match.

Do not forget that the release strategy for a purchase order is a header level release strategy and your field BSGRU is a item level field, which is especially a bit problematic if your PO has more than just 1 item.

Your code example from above has no active statement, all lines are comments.

Show 4 Share
10 |10000 characters needed characters left characters exceeded
Former Member

We have other characteristics also like doc type , plant , pur.org, pur.grp , value and we are trying to add the new characteristic which is a item level field ( assuming all po line items have same code ).

Even I removed the characteristic and commented the code , but the previous version of release startegies are not working , please advise.

0

These are just empty words, they do not explain how your classification looks and whether the values match. The Plant as characteristic is again a value from item level and this needs special treatment in the setup.

Go through my blog

https://blogs.sap.com/2015/01/04/purchasing-release-strategy-an-expanded-explanation-and-a-gps-through-scn-and-sap-notes/

see especially the section Header level strategy

and see the 2 pictures at the very end, this is the information that you gave us so far.

1
Former Member
Jürgen L

Release group Rel. Strategy Release code

PH 01 01
PH 02 02
PH 03 03
PH 04 04
PH 05 05
PH 06 06
PH 07 07
PH Y1 Y1
RG 01 01

I have checked the table T16FS , it shows the release strategy 01 is exist under groups RG and PH , but I could not found in the config those entries , please advise how to delete the entries if it causes the disappearing of release tab in PO.

0

this issue was also discussed some hundred times already, and it was explicitly addressed in my blog too, read the section No changes

0