Skip to Content
avatar image
Former Member

DEBMAS07 IDoc posting solely in upper case

Good morning!

We are creating a new interface to maintain master data within SAP for invoicing, from an external system. I am in the development stage and have noticed that when posting an IDoc using IDOC_INPUT_DEBITOR, the name, address fields etc are all upper case after posting. The content of the IDoc is a mixture of upper and lower case. I suppose this is standard behavior, but its not ideal from an end user perspective. Anything we can do about this?

The scenario is receive a SOAP message, convert to the DEBMAS07 structure in PI and create an IDOC in ERP to post via function module IDOC_INPUT_DEBITOR.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 07, 2017 at 09:05 PM

    Did you already check the content of the Idoc in WE02 or WE05?

    Is it already in upper case in the Idoc or does it become upper case after processing the Idoc?

    If it is already upper case in the Idoc then it must probably happen when you convert your SOAP message into an Idoc. (assuming that it is not already upper case in your SOAP message). The Idoc itself is nothing else than a truck, a carrier for data.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Jurgen,

      Cheers for the reply. For ease/quickness of testing/discovery i am doing this directly in WE19.

      But due to your comments I did just look at the processed IDOC's via BD87 and can see that they are all in Upper Case... Which is not what I put in the IDoc structure in WE19 (I put in a mix - mostly lower case).

      Would you expect this behaviour?

      I'll step through the FM on debugging now to have a quick scan of what is going on.

      EDIT: Apparently it is upper case in the SDATA as soon as i hit the function module :/

      If i actually create the integration scenario properly via PI and ALE config would this occur?

      I have just done a bit more reading and apparently SAP have noted this behaviour within WE19... So this is infact an invalid question as it is working as designed. Thank you for tipping me in the right direction.