Show TOC

XML File Port Type: Maintaining the Port DefinitionLocate this document in the navigation structure

Procedure

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 Start of the navigation path SAP Menu Next navigation step Tools Next navigation step IDoc Interface/ALE Next navigation step Administration Next navigation step Runtime Settings Next navigation step Port Maintenance (WE21) End of the navigation path.

  2. Position the cursor on XML and choose . Enter a name for the port and confirm your entries.

  3. Enter an informative text as the Description.

    The text is displayed in the initial screen of the port definition and in the partner profiles. An example of a descriptive text would be "Files contain the DTD".

  4. Select the XML format.

    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 schema is provided, meaning that DTD embedding is also no longer necessary.

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

    The DTD contains the tags that are used in the following XML IDoc, in other words, 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. It might be necessary to convert national special characters such as ä,ö and ü into internationally recognized character strings such as ae, oe or ue. You must also maintain the Conversion Table and then select Convert Special Characters. Please remember that the character strings in the segment fields can then change length.

  7. As with the "file" port type, it is best if you enter a function module that generates the file names. SAP recommends EDI_PATH_CREATE_CLIENT_DOCNUM or EDI_LPATH_CREATE_CLIENT_DOCNUM for logical directories. These function modules guarantee unique file names and therefore prevent the overwriting of files that have not been processed. Perform an access test for your directory.

    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 test tool ( Start of the navigation path WE19 Next navigation step Settings End of the navigation path), and you have not specified a function module, then the static name is used in the test programs. 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. Tab page Outbound: Trigger: Proceed as in step 6 with file port type. Perform another access test .