In one of our actions we are updating volume in an already created STO via a BAPI. We perform an explicit BAPI commit as well as set the action to perform a commit after each function in AIF configuration.
The next step is to create a delivery document - we're using a BAPI to do this as well. The problem is that the BAPI is not seeing the newly updated data - it's being created with the old STO data.
Any ideas on how to make sure the next function in the action will read the updated data?
BAPIs being used:
Update STO: BAPI_PO_CHANGE
Create Delivery: BAPI_OUTB_DELIVERY_CREATE_STO
We have a separate action that CREATES the STO and then CREATES the DELIVERY and that works fine.. It seems to just hiccup on reading the updated STO data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.