cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

MII12.1 Issue - Data Item

0 Likes
211

Hi,

I created a simple transaction with

Document-->"Reason" field added through configuration.

Column-->Documnet.output is selected in configuration and Name = "Line" and Data Type =Double

Row -->Document.output in config and in Links "Reason" is assigned to the string "Reason1".

and DataItem -->Documnet.output is selected in config and in Link editor Name="Line" and Value=10

Gives output as:

Reason | Line

Reason1 | 10

Works fine in MII 12.0.6 Build(12)

The same transaction I created in MII 12.1.0 Build(201) It does not insert the values in the columns and add extra rows.

Output in MII12.1:

Reason | Line

Reason1 | --

-- | --

There is an issue with Data Item action block in MII 12.1. Pl help and give feedback.

Thanks and Regards

Khaleel

Edited by: Khaleelurrehman Badeghar on Oct 28, 2010 12:09 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Likes

Hi Khaleel,

this sounds like a MII error to me. The Data Item should add a column value to the current row which has been created by the Row action. As an alternative you can try the following:

- add an empty row (do not add the items)

- use Data Items to add both column values

does this makes a difference?

However, you should also consider to upgrade your MII version 12.1.0, as there have been lots of bug fixing for 12.1.

Michael

0 Likes

Hi Michael,

Thanks for your response. I checked as suggested by you. But column values are not inserted by data item.

Thanks and Regards

Khaleel

Former Member
0 Likes

Hi Khaleel,

finally you can try one small variation:

- create a XML document without columns

- define your columns using the column action

- create an empty row

- add the Data Items

Maybe this will be handled differently. If not, you should consider to open a SAP ticket.

Michael

jcgood25
Active Contributor
0 Likes

There is no point in opening a support ticket since the 12.1.0 version is the initial ramp up release.

@Michael - your earlier recommendation to upgrade to the latest 12.1 service pack/patch is the right path forward - even if you're still chugging away on 12.0.2

In the off chance that this is actually still an issue in the latest 12.1 patch, the problem cannot be patched against that old release.