Transmitting text in IDoc

[gajendra_bhakuni]

Hello,

I have a scenario wherein I have text object (like sales text in Material master) attached to an IDoc.

I want to transfer text that the user enters (within SAP) via IDoc to XI. XI then need to call a webservice and post this text information to the webservice.

Later the legacy application returns some text back and this needs to be mapped by XI to inbound Idoc which will be posted within SAP.

Can you propose some protocol/mechanism to handle such scenario.

I looked at the MATMAS03 Idoc. There we have segments E1MTXHM (long text header) and E1MTXLM (long text line). Within the E1MTXLM we have TDFORMAT which will take care of formatting the text.

Now I need to put some logic in XI mapping or within legacy application to read these formatting information in IDoc and make full text lines out of it and post it into legacy application.

Similarly in the inbound side the Legacy text needs to mapped to the incoming idoc (with proper codes filled in TDFORMAT) and posted into SAP.

How feasible is this approach? Any other better way to handle text transmission?

Any help in this regard is highly appreciated.

Regards,

Gajendra.

[Former Member]

What is the problem you are facing here?

Seems to be a simple IDOC-WS-IDOC scenario.

Is there a problem with text formatting? If so, explain that briefly here.

Regards,

Jai Shankar

[gajendra_bhakuni]

Problem is:

1) Where to put the logic for decrypting the text in idoc to proper text lines which legacy can understand and post.

2) On the inbound side somewhere we need to map the text which legacy sends into IDoc.

3) Is this a good approach? Can we think of publishing the text information at some website from where the legacy can pick it up and read?

4) The scenario looks simple but I see some complication arising in mapping back and forth.

Regards,

Gajendra.

[Former Member]

>1) Where to put the logic for decrypting the text in idoc to proper text lines which legacy can understand and post.

I dont understand this part. Data from IDOC is in text format only.

In XI you can do data conversion (mapping) which is transforming the data in Sender format to a format readable by the receiver. There are different mapping techniques available. Use the one that suits you better.

>2) On the inbound side somewhere we need to map the text which legacy sends into IDoc.

Again this is done with in XI mapping.

>3) Is this a good approach?

Yes it looks to be. But this has to decided based on the business process. So I cant comment on this with out a good understanding of your business requirement.

Regards,

Jai Shankar

[gajendra_bhakuni]

Hi Jai Shankar,

Thanks for providing inputs.

The Business scenario is that SAP needs to communicate the text to a legacy application and the legacy application can later modify the text and send it back to SAP.

How complex is the XI mapping and joining of SAP text (broken down into idoc segments) and vice versa (taking the modified text from legacy application and posting it into SAP segment with proper formatting codes).

Regards,

Gajendra.

[prateek]

If the issue is just transmission of the text, then the mapping wont be much complex. The standard functions of graphical mapping would be enough. And some custom functionalities can be easily achieved using user defined functions

Regards,

Prateek

[prateek]

The approach is feasible using BPM. U start with the sender Idoc. Receive the data and then perform the mapping with the SOAP Request structure. U may use UDF or java mapping for formatting of the texts. The mapped request is then sent using a synchronous send step. The response is again mapped to the Idoc structure. Again the UDF or java mapping can be used. Then send the data finally to the SAP system using a send step.

Regards,

Prateek