cancel
Showing results for 
Search instead for 
Did you mean: 

some quesionts about message mapping

Former Member
0 Kudos

becase I need use some pics to explain my question, so I post the question to my googlepage.

<a href="http://wanghui1225.googlepages.com/xi_question_1">http://wanghui1225.googlepages.com/xi_question_1</a>

Regards,

Hui

Message was edited by: Wang Hui

Accepted Solutions (1)

Accepted Solutions (1)

former_member187339
Active Contributor
0 Kudos

Hi,

Since you are using collapse context, the SUPPRESS is coming. Functionality of collapse is it delete all values from all contexts from the inbound queue except for the first value. <b>Empty contexts (= ResultList.SUPPRESS) are replaced by empty strings.</b>. Finally, all internal context changes are deleted, so that all values belong to one and the same context.

Give the input queue for collapseContext, then it will be really helpful.

See the input queue had 3 true's followed by false (2) and true (2). As you can see that the starting context itself is false and so SUPRESS came in the output queue.

What i suggest is to check all these queues simultaneously:

1) exist

2) context

3) splitbyvalue

with different values then you will be able to figure out the reason.

Regards

Suraj

Message was edited by: S.R.Suraj

Former Member
0 Kudos

hello Suraj,

I have updated link, now you can get the input queue for collapseContext

Regards,

Hui Wang

Former Member
0 Kudos

>>>>As you can see that the starting context itself is false and so SUPRESS came in the output queue.

I am confused by the value of starting context. I have read SAP help, which said a context change is represned by ResultList.CC. So how can a context have some value rather than Result.CC?

Another question is: the first element of each input queue for each source field is always SUPPRESS and grey. And the value of internal contexts are always the identical to the value of the previous element.

Could anyone give some light?

Regards,

hui

Answers (0)