During runtime, information defined in the TPM can be accessed in the following manner:
  • You need to add TPMContentAccessModule in your Integration scenarios wherever you have EDI document processing.

        Important ℹ : You must use enable.edisepUsage parameter as a precautionary step, before using TPM content access module parameter.

  • Set enable.ediAckProfile to true. This parameter when it is set to true is required for applying the TPM settings to EDI Separator Receiver channel. The module reads parameters from TPM related to EDI acknowledgment settings and publishes them to PI processing pipe-line. This parameter needs to be set for the TPMContentAccessModule only in the ICO(s) where EDI Separator receiver channel is used.
  • Depending on the Inbound/Outbound EDI processing, you need to add this module either on sender or receiver side respectively
  • This module should be added before generic converter module. Set the value of module parameter tpm.enable of genericConverterModule to true. It will then fetch the control Key info and module parameters as per TPM agreement.
  • Enable the checkbox Read From Dynamic Header in EDI Separator receiver channel to apply the TPM settings

Important ℹ : In case if you are using EDISearchParametersModule, then it should be used in order such that it is before genericConverterModule and used after TPMContentAccessModule. It is recommended to use EDISearchParametersModule as it enables monitoring based on sender ID, receiver ID, interchange number, and correlation number.

TPMContentAccessModule when added does the following:

  1. Enable monitoring related parameters in XI message headers so that you can create UDS in local message monitoring and enable search.
  2. Enable acknowledgement related settings from TPM so that EDI Separator can apply the settings.
  3. Enable module related EDI parameters as defined in TPM agreement
  • You can create the UDS and enable search on the following parameters from TPM.
  • Sender Partner and Receiver Partner Information is set based on the sender and receiver ids from the Inbound/Outbound EDI message
  • Partner Name information is set  based on the following:
    1. For Inbound EDI messages, sender id is considered
    2. For Outbound messages, receiver id is considered.

PartnerName

SenderPartnerName

ReceiverPartnerName

PartnerType

SenderPartnerType

ReceiverPartnerType

PartnerIndustry

SenderPartnerIndustry

ReceiverPartnerIndustry

PartnerRegion

SenderPartnerRegion

ReceiverPartnerRegion

PartnerParentGroup

SenderPartnerParentGroup

ReceiverPartnerParentGroup

PartnerPIParty

SenderPartnerPIParty

ReceiverPartnerPIParty

Note While creating an UDS, you have to use the following Dynamic header namespace http://sap.com/xi/XI/EDISeparator/EDISeparator

Related Links

See the following links for more information:

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply