It consists of two major steps:
-
Create ( or update ) equipment in CRM -
Create ( or update ) equipment hierarchy in CRM
After step1, there is an save operation performed on all equipment involvled in current BDOC. Instead of performing the object one by one, all objects are saved by the function module in a single shot. Before the save is actually performed, there is a check logic which will abort the real save if there is anything wrong ( to be more exact, there is message with type ‘A’ or ‘E’ ) with the object data to be saved. For example if there is Nequipment in the BDOC, and there is one ‘A’ or ‘E’ message raised during create or update operation on a single equipment in CRM, then the save operation on these N equipment will not get executed at all – could be regarded as an atom operation: eithter save all, or save none.
You can set breakpoint on include LCOM_PRODUCT_MAINTAIN_APIF10, line 30, and check internal table et_bapireturn in line 32.
There are three message with type ‘E’ which will abort the save operation ( mark the cv_save with off in line 42 ).