CRM_Order_maintain & Crm_order_save.

[prav_kr]

why they have developed the system like this ::

First you have to call ORDER_MAINTAIN to change in buffer

then ORDER_SAVE to save and THEN Transaction_commit  (or commit work) to commit work.

Why this three step process ??

Instead they may have an another import parameter in ORDER_MAINTAIN itself to confirm

NO_COMMIT_save = 'X' (Not ot commit and save )or  NO_COMMIT_save = ' ' ( to save)..

[ThomasZloch]

General reply, because I don't know these specific function modules:

Usually the caller (same or remote box, ABAP or other language) must decide after the first call whether to commit or rollback the changes done, often based on returned messages. Also you might want to chain several changes before committing.

So it is more flexible to split these actions into several steps that can be called separately.

Thomas