BAPI_PO_CHANGE Issue : Release Tab disappears in PO Screen !

[Former Member]

Hi All,

I am using BAPI_PO_CHANGE to add new line items with reference to the PR given as an input through excel sheet .

After the Program execution , Line items get added successfully ,

BUT the Release Strategy tab does not appear any more in the ME23N screen .

If we make a slight change in the PO , e.x .  put a dot or something in some text field and save ,

Tab appears again .

My concern is how to change the PO using BAPI ,  by still keeping the release strategy tab .

Is there any Note or exit for that ?

Kindly suggest .

Regards,

Hemant

[former_member186099]

hi Hemant,

Check whether you are passing the BAPI parameters in such a way that PO/PR is already released before you check the changes in ME33N, this could be the reason. BAPI and ME32N should behave the same way.

Regards,

Prasanna

[Former Member]

Hi Prasanna ,

I am not passing any parameter related to release strategy to the BAPI .

I have tried running the BAPI with both the cases :

1. Passing release indicator in header

2. Without Passing release indicator in the header .

Its not making a difference .

Regards,

[former_member222709]

Hi Hemant,

The Release Strategy Tab is displayed whenever the system finds the PO is applicable for a Release Strategy.

In your case, I believe, even though it is applicable, the Release Strategy tab appears only after any activity done from ME22N.
1. But, is this happening for PO's that are completely released?

2. when you call the BAPI, is the PO on hold?

3. Are you passing the Condition or Pricing internal table to the BAPI that triggers in blocking the Release status of the PO?

4. Finally, is there any User Exit or Enhancement that has been done in the standard transaction for setting the Release Strategy that needs to be incorporated in the BAPI?

Regards,

Pranav.

[former_member186099]

hi Hemant,

Can you post the logic which fills up the header parameters? When u checked the release strategy parameters using BAPI, did you pass the value X in header change structure?

Cheers

[Former Member]

Hi Pranav ,

Answers to your queries are as :

1. 1. But, is this happening for PO's that are completely released?  -- For all cases (released & unreleased both)
2. 2. when you call the BAPI, is the PO on hold?   -- No – this is change in existing PO (may be open or partially processed)
3. 3. Are you passing the Condition or Pricing internal table to the BAPI that triggers in blocking the Release status of the PO?   -- Yes we are passing pricing conditions simultaneously. 
4. 4. Finally, is there any User Exit or Enhancement that has been done in the standard transaction for setting the Release Strategy that needs to be incorporated in the BAPI?  -- -- No

regards,

[Former Member]

Hi Prasanna ,

Yes we passed the value X in header change structure also .

We tried without passing X also .

In header info we are currently passing only : PO number and nothing else .

Regards,

[former_member222709]

Hi Hemant,

Since you have ruled out most of the possible cases, try passing the following parameters to the Header Structure:

1. POHEADER-PO_NUMBER

2. POHEADER-DOC_TYPE

3. POHEADER-PO_REL_IND --> (Corresponding value for Blocked)

4. POHEADER-REL_STATUS --> (Creator as per configured Release Strategy).

&

POHEADERX-PO_NUMBER = POHEADERX-DOC_TYPE = POHEADERX-PO_REL_IND = POHEADERX-REL_STATUS = 'X'.

Regards,

Pranav.

[Former Member]

Hi ,

As mentioned by Pranav earlier :

about the various scenarios that can be possible for the issue :

Scenario 4 : was the root cause in my case .

Finally, is there any User Exit or Enhancement that has been done in the standard transaction for setting the Release Strategy that needs to be incorporated in the BAPI?

In one user exit toggling has been done .

Thanks for the support . Issue Resolved .

Regards,