ORDER_MAINTAIN Change Opportunity in Web DynPro Applikation ORDER_SAVE

[Former Member]

Hi Gurus!

I've written a WDA to display and modify Opportunities.

After the User has changed e.g. the Description of the Opportunity and wants to save, the WDA performs following steps:

importing IT_ORDERADM_H type CRMT_ORDERADM_H_COMT (LS_ORDERADM_H-DESCRIPTION has changed for example)

ls_input_field_names-fieldname = 'DESCRIPTION'.

append ls_input_field_names to lt_input_field_names.

ls_input_fields-objectname = 'ORDERADM_H'.

ls_input_fields-field_names = lt_input_field_names.

ls_input_fields-ref_kind = 'A'.

ls_input_fields-REF_GUID = ls_orderadm_h-GUID.

append ls_input_fields to lt_input_fields.

ls_objects_to_save = is_orderadm_h-object_id.

append ls_objects_to_save to lt_objects_to_save.

CALL FUNCTION 'CRM_ORDER_MAINTAIN'

CHANGING

CT_ORDERADM_H = lt_orderadm_h

CT_INPUT_FIELDS = lt_input_fields

CALL FUNCTION 'CRM_ORDER_SAVE'

EXPORTING

IT_OBJECTS_TO_SAVE = lt_objects_to_save

IMPORTING

ET_SAVED_OBJECTS = lt_saved_objects

ET_EXCEPTION = lt_exceptions

ET_OBJECTS_NOT_SAVED = lt_objects_not_saved

Thats it. There are no exceptions and all lt_saved_objects, lt_exceptions and lt_objects_not_saved are empty. but nothing is saved in the orderadm_h table!

Where is the problem in that?

Thanks in advice.

Farid

[Former Member]

commit work

[Former Member]

solved the problem.

just keep in mind to commit work after changes. that's all.