Entering content frameProcedure documentation Port Type XML: Maintaining Port Definition Locate the document in its SAP Library structure

The regulations for generating the outbound file are defined in outbound processing. In inbound processing, the port definition only affects the test program (see below).

  1. Choose SAP Menu ® Tools ® Business Communications ® IDoc Basis ® Administration ® Port definition.
  2. Position the cursor on XML and choose This graphic is explained in the accompanying text. Name the port and confirm your entries.
  3. Specify a text that is as descriptive as possible in the definition.

    4. The text is displayed in the initial screen of the port definition and in the partner profiles. A descriptive text, for example, would be "files contain the DTD".

  4. Select the XML format.

    5. Note

    If you choose Unicode as the XML format, continue with step 7. Conversion of national special characters is no longer necessary and an XML procedure is provided, therefore DTD embedding is no longer necessary.

  5. On the Outbound File tab page, you can choose whether the IDocs should be written together with the corresponding Document Type Declaration (DTD) in the XML file.

    6. The DTD contains the tags that are used in the following XML IDoc, that is, tags for the IDoc record types and the individual segments. The tags are named in the same way as the individual fields. The start-end-tag-sequence for the field MESTYP of the control record EDI_DC40 is therefore <EDIDC_40-MESTYP><EDIDC_40-MESTYP>.

  6. If possible, you must replace country-specific special characters such as ä,ö,ü with international characters like ae,oe,ue. You must also maintain the This graphic is explained in the accompanying text Conversion table and then select Convert special characters. You must note, however, that the character strings in the segment fields can then change length.
  7. As with port type file, it is best if you enter a function module which generates the file names. SAP recommends EDI_PATH_CREATE_CLIENT_DOCNUM or EDI_LPATH_CREATE_CLIENT_DOCNUM for logical directory. These function modules guarantee clear file names and therefore prevent files that have not been processed from being overwritten. Perform an This graphic is explained in the accompanying text access test for your directory.

    8. The file name generated by the function module overrides the static name, which you can maintain in field Outbound file. A static name can make sense for a test port: If your test port is entered in the corresponding field in the IDoc administration, and if you have not entered a function module, then the static name in the Test programs is used. Static file names like dynamic file names contain the addition .xml in Windows/NT operating systems.

    Logical directories are resolved depending on operating system in the physical directory maintained in the transaction FILE. Also see the F1 Help for the logical/physical directory fields.

  8. Outbound: Triggering tab page: Proceed as in step 6 with Port type file. Perform another This graphic is explained in the accompanying text access test.
Leaving content frame