Configuring ePM: ToPartner and FromPartner Messaging Model

The following list explains the outbound and inbound messaging model used for Environments and TPs during ePM configuration:

• When you are configuring ePM for a component related to the current TP’s Environment, you must take the viewpoint of that Environment.

  For example, Company A is the current TP with its own Environment. You are configuring a component related to Company A’s Environment envA. Therefore, in terms of the companies, ToPartner means from Company A (outbound from envA) and FromPartner, to Company A (inbound to envA).

• Following the same model, when you are configuring ePM for a component related to a different TP’s Environment, you must take the viewpoint of that Environment.

  For example, Company B is a TP with an Environment outside of Company B. You are configuring a component related to Company B’s Environment envB. Therefore, in terms of the companies, ToPartner means from Company B (outbound from envB) and FromPartner, to Company B (inbound to envB).

• Therefore, if TPs in the previous examples are named as follows:

• tpB is Company A’s TP.

• tpA is Company B’s TP.

  The following relationship holds true:

• tpA is the TP for envB.

• tpB is the TP for envA.

ASC X12 PM-specific Parameter Types

ASC X12 PM-specific parameters are of two basic types as explained under:

• Interchange Envelope Parameters

• Functional Group Parameters

  ---

  Note –

  When ePM displays both sets of parameters in the previous list, parameters appear, which are generic to eXchange and are not explained in this chapter. See the eXchange Integrator User’s Guide for details on these parameters.

  ---

For additional information on how to configure ePM parameters, see Importing and Configuring Components in ePM, as well as the eXchange Integrator User’s Guide.