cancel
Showing results for 
Search instead for 
Did you mean: 

SAP TM - request Standard action Split/Merge FU from a UI5 Portal

abeln
Discoverer
0 Kudos
1,276

Hello,
We are using a UI5 Portal (hosted on BTP) to edit Freight Units. One action will be Split/Merge FU, which is a SAP Standard action in the FU. We just want to trigger it from a Portal. Everything is developed and performing well, but when we want to save the FU, the changes are not saved.

Please check our screenshots below.

To rebuild this functionality, we use the action ‘BUILD_FUS’ from the Root node of BO ‘/SCMTMS/FUB’. The parameter structure ‘ls_fub_build_params’ is filled just like the one during FU-Split from the NWBC.

To rebuild this functionality, we use the action ‘BUILD_FUS’ from the Root node of BO ‘/SCMTMS/FUB’. The parameter structure ‘ls_fub_build_params’ is filled just like the one during FU-Split from the NWBC.

Afterwards we check if the FUB instance has changed. The result is that a specific quantity (1 PC in our case) is split off the initial FU (4000000859) and a new FU (4000002994) is created, what is exactly what was expected:

The ‘FUB_RESULT’ also shows two Freight Units as a result (one that is newly created and one that is updated):

When saving the current transaction via transaction manager, the message ‘/BOBF/LIBRARY – 019’ is returned, which says that no changes have been made.

So, we fail to persist the FUB result to the database since the transaction manager does not notify the changes (creation and update of Freight Units).

Thank you for your support.


Accepted Solutions (0)

Answers (2)

Answers (2)

abeln
Discoverer
0 Kudos

Hi Emanuel,

thank for your reply. We remved the "accept_solution" call and adjusted some parameters of the FU-Building action and now the split is working.

Thank you for your input and quick reply!

GRABLERE
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Simon,

can you try to skip the "accept_solution" method call. This method should only be required when working with buffer variants, as the UI is doing(so we can roll back in case of reject). As you are actually not working with buffer variants, I suspect that accept solution is maybe actually doing the oposit and rolling back to original buffer variant.

Let me know if that helped.
Regards,

Emanuel