In my current project, we are on Single Stack SAP PO 7.4 , B2B add-on SP02 Patch 10. In course of our EDI developments(we are dealing with ANXI X12 documents mostly), we noticed that the XSD generator does NOT list all EDI message versions we may need or your client is currently trading with their partners. We did some research, raised an SAP incident and got to know about SAP Note 1934041. Thought of sharing this to the community and also to receive feedback on whether this approach has been implemented by anyone already and if so, get their comments or feedback to what i have detailed below. Now, lets take an example of an EDI 855 document for which we need the XSD for version 002000(this version is not listed in the default control key SAP in b2bic). The steps to get this XSD are below.
1) Goto B2B integration cockpit - http://<host><port>/b2bic.
2) Select EDI content Manager -> Editor -> Message Editor
3) Select a version & set that you would like to copy(in my example scenario i chose to use version 002003 and set 855), Now select "copy control key".
4) select copy control key and in the popup window that appears, specify a new control key, description & also specify the new message version you need, in our example, we need 002000
5) After you save, you should see the new message version against the new control key you specified. There is a step to validate if its good, the pdf attached in SAP note 1934041 should guide you better on the validation.
6) You could then navigate to the control key scenario association under EDI content manager -> Editor and insert a new entry in the table shown in the screen. You should take care NOT to have all of the columns wildcarded, looks like these entries are used by EDISeparator for routing.
7) So for the new control keys & message versions we generated, we specify the exact sender component , service interface etc so that this entry is only confined to a specific interface where its needed.
8) Now, when you navigate to the XSD generator option under ANXI X12 , you should be able to select the new control key from the drop down and once you do so, see the new version we just generated. In our exmaple, it is EDI 855 message version 002000.
9) You could generate the XSD ande then use it in your mapping developments.
Now, I don't fully know the significance of steps 6 & 7 above and does it matter if i skip them. We are in the course of designing the mappings and as i find out more in course of our testing, i will update this post. Thanks for reading this through and provide your feedback if you think we have to course correct anywhere. And if in case, this has already been discussed or written about, i will be happy to add a reference to that post, just let me know.