Idoc extension for eewb custom fields for BUS20001

Question

Hello.
I have an almost exact question as , but I still need to ask what I'm supposed to do.
We've done enhancements in EEW and I can see some append structures in CRMXIF_BUSTRANS (for example). The problem is that when I generate outbound idoc the sturcture E101CRMXIF_BUSTRANS is missing the corresponding append structures.
Why isn't EEW adding this, or do I have to generate/re-generate something?
I've tried to Cancel release/release the ALE interface in BDFG, but with no results.
I think the replications (initial load and delta load) to r/3 has all EEW modifications, but when it comes to idocs, it woun't change.
Is the only solution to create a new idoc in bdfg and create a z-structure?
The FM ALE_CRMXIF_ORDER_SAVE_M used for populating the idoc, would work if the structure E101CRMXIF_BUSTRANS was extended with the same appendstructure (since the only thing it does is a move-corresponding...).
So, the question is if I have to create a new z-idoc, or if it's possible to regenerate the structure used in the idoc segments?
Regards, Mikael Löwgren

Answer 1

Hi,
When you have ignored the inconsistencies, this means the complex structure fields and the corresponding Idoc Segment fields are different in the support package.
If this is the case, when the Idoc is regenerated in Tx BDFG, you will find the message type will be in
error when you press F9 to do the syntax check.
There you will see the segments which are in error as well as the 'Interface is not current and it must be regenerated' error message.
Check those segments listed in syntax check against the respective complex structure. If there are differences like if some fields are added or the data element is changed, kindly correct the segment fields via Tx IDOC.
If you need to add fields to the segment, you need to increase the field length of the segment in EDISDEF table, which can be done in Tx IDOC --> Repair segments tab --> Change entries in EDISDEF table.
There you can change the field length and then change the entries in EDSAPPL table.
Similarly if you take out all the errors in the segments listed for a particular message type and try to release the Idoc, it will be released without any errors.
This happens, as far as my understanding goes, mainly because the complex structures might under go some changes from the development side but not the Idocs. Since both are different entities, mostly these types of things happen.
Do let me know  if this has helped you.
Venkat