Creating a parameter definition for a publishing service

To create a parameter definition for a publishing service:

  1. Select Transformation Services > Configuration > Publishing Services.
  2. Click Create.
  3. Specify this information in the Detail field set:
    Effective from Date
    This field defines the start date of the valid period for the configuration.
    When editing, click the Calendar button to select the start date from a calendar.
    Effective to Date
    This field defines the end date of the valid period for the configuration.
    When editing, click the Calendar button to select the end date from a calendar.
    Partner Hierarchy Name
    The partner hierarchy name is a classification for a group of communication partners. A partner hierarchy must exist for this configuration.
    Partner ID
    The partner ID is the hierarchy node of the configuration that identifies a communication partner or a group of communication partners.
    Message Type
    The message type defines the content of the message. Examples are VDA 4905, VDA 4915, ASC X12 830 Planning Schedule with Release Capability, or ASC X12 862 Shipping Schedule. The message type depends on the message standard.
    Note: For trading partners who require the Shipment Cancellation message to be sent to a different data source name (i.e., final recipient) than the regular shipment, a new code list must be activated in FeatureActivation code list. On this code list, add the Code value UseShipmentCanceledMessageType. Activating this code results in process shipments with the status of Canceledto be created as messages with the message type Shipment Canceled BOD instead of Shipment. See Configuring ASN cancellation and replacement for more details.
    Message Direction
    The message direction is Inbound for incoming messages or Outbound for outgoing messages.
    Publishing Service
    The publishing service specifies the target system to which a message is published.
    • EXS: Transformed messages are published to Exchange Services and sent to an external communication partner.
    • ION: BOD messages are published to ION.
    • File System: Transformed messages are published to the file system.
    • No Publishing: The messages are not published.
    Accounting Entity
    The accounting entity is a corporation or a subset of a corporation. The accounting entity is independent in regard to one or more operational functions or accounting functions. An accounting entity produces a P&L and balance sheet from a complete, balanced set of transactions, and is often a legal entity. An accounting entity is defined within a tenant and can contain locations. The field entry is disabled. The accounting entity is automatically set when you save the data. The default is the accounting entity where you are currently working.
    Review or provide a short description that clarifies the purpose of the configuration.
  4. Specify a comment on the parameter definition for the publishing service in the Note field set.
  5. If you select the publishing service File System, specify this information in the File System Parameters field set:
    Export File Path
    Specify the path name that is used by Transformation Services to store the transformed messages. The path name is required.
    File Prefix
    Specify the prefix of the file names. You can use a prefix for file names to differentiate between files of miscellaneous message types or partners that are stored in the same directory.
  6. To save the parameter definition, click Save.
    A notification displays that the publishing parameters have been saved successfully.