Channel Distribution CheckMsconsManualTransaction

Overview

With CheckMsconsManualTransaction you can distribute MSCONS messages over their type.

Class: org.b2bbp.channels.extension.CheckMsconsManualTransaction

Type of Channeldistribution

Type  
APERAK-Check  
Pattern Based Channeldistribution X
Display Short Text Channeldistribution  
Hard Coded Channeldistribution  
Other  

Additional Entries in MessageContext

Key Value Description
MSCONS_CAT BGM-D1001 Value of document name

Used Pattern Key

RECD_MSCONS_MAN_TRANSACTION

Examples

No Forwarding

RECD_MSCONS_MAN_TRANSACTION.pattern=${template(&(this.MSCONS_CAT)_&(this.partnerCode))}

RECD_MSCONS_MAN_TRANSACTION=BK_0123456789123=INBOUND_MSCONS_BK

RECD_MSCONS_MAN_TRANSACTION=7_0123456789123=INBOUND_SAP

Explanation: All MSCONS from type „BK“ to partner 0123456789123 are distributed into channel INBOUND_MSCONS_BK, all MSCONS from the type „7“into channel INBOUND_SAP. All the others aren’t distributed.

Forwarding

RECD_MSCONS_MAN_TRANSACTION.pattern=${template(&(this.MSCONS_CAT)_&(this.partnerCode))}

RECD_MSCONS_MAN_TRANSACTION=BK_0123456789123=INBOUND_MSCONS_BK,test@test.de

RECD_MSCONS_MAN_TRANSACTION=7_0123456789123=INBOUND_SAP

Explanation: Distribution as in 7.1, but to all MSCONS from the type „BK“ to partner 0123456789123 there is in MessageContext an additional value “test@test.de” at the key B3P_FORWARD_MAIL_TO.

View Me   Edit Me