Solution Manager
Page tree
Skip to end of metadata
Go to start of metadata

XML File on Application Server

Run Mode: BACKGROUND AND DIALOG Aggregation: GENERIC AFTER EXTRACTION Iteration: SUPPORTED Duplicate Check: NOT SUPPORTED 

Metadata retrieval: NOT SUPPORTED  Extraction Strategy: INDUVIDUAL SELECTION AND KEY BASED SELECTION Special Permissions: NONE

 

No generation, extracts data from XML files on application server of SAP Solution Manager, compares data in SAP Solution Manager.

You choose this for data that is stored in a XML file on an SAP Solution Manager application server. The source type is able to process single and multiple XML files.

Parameters

The following data is required:

ParametersDescription
Host nameSpecify the name of the application server
File PathSpecify the path on the SAP Solution Manager application server under which the XML file containing the data to be compared is saved.
File NameSpecify the name of the XML file. In no file name but only a path name is supplied, all files in the given path are processed. Moreover, the file name allows wild-cards *, +, $TODAY and $YESTERDAY. In case multiple files are selected, data from all these files is processed together.
Created from, Created to

Enter a time from when and a time until when files are considered. The following key words are possible for entering the times:

    • $TIMES – timestamp now with offset in seconds (example: $TIMES-10)
    • $TIMEM – timestamp now with offset in minutes (example: $TIMEM-30)
    • $TIMEH – timestamp now with offset in hours (example: $TIMEH-12
    • $TIMED – timestamp now with offset in days (example: $TIMED-1)
XML transformationEnter a parameter in order to execute an XLS transformation which changes data from a different format to the required asXML format. In this way it is now possible to process XML files which are originally not in the required as XML format.

Requirements

The CDC source type FIXS for XML files on application server requires either XML files directly in asXML format or XML files in any different format and a corresponding transformation to bring the required data from these files into asXML format.

asXML is the format that you get if you use transformation ID for an internal ABAP table. The following is an example for one item with columns PARTNER, NAME_LAST and NAME_FIRST. (For a table with multiple items, you would see multiple <item> tags.)

The XML declaration at the beginning of the file is optional, whereas the namespace definition needs to refer to ABAP XML. The part of the XML file containing the data to be compared needs to be included in tag <asx:values> (and </asx:values> respectively).

Beyond this level a tag <TABLE> marks the start of the data table, whereas several tags opening and closing with <item> (and </item> respectively) mark the beginning and the end of a line item in the table to be compared.

Within the <item> tags the names of the respective table fields need to be used as tag names. These tags contain the actual item data.

Furthermore it is important that the tags in the XML file in asXML format must correspond to the tags in the mapping connection of the CDC data model.

Example

ABAP Table:

FIRST_NAME

LAST_NAME

CITY

Jason

Li

Shanghai

Peter

Meier

Berlin

Michael

Smith

Washington

Converted into asXML this table would look like this:

<?xml version="1.0" encoding="UTF-8"?>
<asx:abap xmlns:asx=" http://www.sap.com/abapxml" version="1.0">
<asx:values>
<TABLE>
<ITEM>
 <FIRST_NAME>Jason</FIRST_NAME>
 <LAST_NAME>Li</LAST_NAME>
 <CITY>Shanghai</CITY>
</ITEM>
<ITEM>
 <FIRST_NAME>Peter</FIRST_NAME>
 <LAST_NAME>Meier</LAST_NAME>
 <CITY>Berlin</CITY>
</ITEM>
<ITEM>
 <FIRST_NAME>Michael</FIRST_NAME>
 <LAST_NAME>Smith</LAST_NAME>
 <CITY>Washington</CITY>
</ITEM>
</TABLE>
</asx:values>
</asx:abap>

In the definition of the data model it should like this:

(Here “TEST_TABLE” is used as table name.)


  • No labels