XIF, Don’t update my CRMD_ORDERADM_H please
Recently I was massively uploading the date profile of Sales Orders via SXDA, LSMW and XIF interfaces (CRMXIF_ORDER_SAVE_U06), basically I needed the segment E101CRMXIF_BUSTRANS using the following fields in order to select the Sales Orders which must be updated OBJECT_ID, PROCESS_TYPE and OBJECT_TYPE. Why don you used the GUID instead? well the standard selects the data using the criteria which I descrived, if you only use the GUID will prompt an error, so at the very end you don’t need to use the GUID because the standard don’t use it.
Going back to the topic, I also needed the segments: E101CRMXIF_APPOINTMENT_XT, E101CRMXIF_APPOINTMENT and E101CRMXIF_APPOINTMENT_F in order to update the date profile of the sales orders, so far so good.
What happend? I uploaded the Sales Orders modifying the date profile, but also the POSTING_DATE (CRMD_ORDERADM_H-POSTING_DATE)
WHY?! I didn’t map the field using the flag segement E101CRMXIF_BUSTRANS_F, well after raising an incident to SAP…tic tac tic tac
The SAP consultant pointed to:
If the segment E101CRMXIF_BUSTRANS_F is completely empty then all fields will be updated – this is special for this segment. Mostly you set an X for each field which should be updated. POSTING_DATE or DESCRIPTION are one of the crmd_orderadm_h fields that are put to the input fields by default
In my scenario I didn’t need to update any CRMD_ORDERADM_H field so I marked the field E101CRMXIF_BUSTRANS_F-OBJECT_GUID and everything worked fine. I hope I can save you some time if you have the same issue. The SAP consultnat said he was planing to create a KBA in order to clarify this so is in his to-do list, and we all know this can be writen today, tomorrow or in one year, all depends on his internal priorities, but meanwhile, you can refer here 🙂