cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BAPI_SALESORDER_CHANGE extension update issue with AEDAT

tony_dagnillo2
Explorer
0 Likes
680

When I use BAPI_SALESORDER_CHANGE to change a Z field in VBAP via the extensionin table parameter it properly updates the field in question. This works for all lines on the order that I need to update. It also updates column VBAP-AEDAT (Change Date). The problem is that it is updating AEDAT for all of the rows in VBAP for this order instead of just the rows where I am updating the Z field. I need AEDAT to only update for rows where I am actually updating the Z field.

I am not passing all the VBAP lines into the extensionin table, just the ones I want to update by passing the populated structures of BAPE_VBAP and BAPE_VBAPX into the extensionin-valuepart1 and extensionin-valuepart2 as needed.

Any advice?

Thanks in advance

Accepted Solutions (0)

Answers (3)

Answers (3)

venkateswaran_k
Active Contributor

Hi Anthonay,

You might have used the extension variable (example)

 WA_BAPE_VBAPX           TYPE BAPE_VBAPX,

In this wa_bape_vbax make sure you pass the appropriate POSNR also before pushing it in BAPI.

Regards,

Venkat

0 Likes

Hi Anthony,

In BAPI_VBAPX, you have to commit this X for two fields one is AEDAT field and another one is POSNR. kindly confirm have you committed X for these two fields.

The same you have entered in BAPI_VBAP for AEDAT and POSNR, the same you have to commit in BAPI_VBAPX.

tony_dagnillo2
Explorer
0 Likes

Yes - I've been doing that.

Thanks,

Tony