Manually importing a message
In cloud environments, you can manually import messages on the Import Messages page.
To manually import a message:
- Select Transformation > Import Messages.
- Click Create to display the detail view of the Import Messages page.
-
Specify this information:
- Partner ID
- The partner ID is the hierarchy node of the message that identifies a communication partner or a group of communication partners. The partner ID is optional in this context and can be used to manually import messages of specific trading partners. Select the partner ID from the drop-down list.
- Message Standard
- The message standard defines the format or structure of the message. Examples are ASC X12, UN-EDIFACT, XML, or BOD. The message standard is optional in this context and can be used to manually import messages of specific trading partners. Select the message standard from the drop-down list.
- 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 is optional in this context and can be used to manually import messages of specific trading partners. Select the message type from the drop-down list.
- Message Status
- These message statuses exist:
- New: A message is created.
- Being Processed: The message is currently being processed.
- Processed: The message is processed and completed.
- Waiting for Transformation: The message is waiting for the transformation.
- Ready to be Published: The message is ready to be published.
- Error: The message transformation failed.
- Waiting for CarrierRoute
BOD: The message transformation is waiting for a
CarrierRoute BOD
to complete theShipment BOD
processing. - To be Processed: The message must be processed.
- To be Deleted: The message must be deleted.
- Message Direction
- The message direction is Inbound for incoming messages or Outbound for outgoing messages.
- Message Sequence Number
- The messages are consecutively numbered in the order in which they are processed.
- Import Service
- These import services are supported:
- ION Connector Service: The message is imported from the ION Connector Service.
- Clipboard Service: The message is copied and inserted over the clipboard and handled by the Clipboard Service.
- Communication Service: The message is imported from the Communication Service.
- Shipping Execution Service: The message is imported from the Shipping Execution Service.
- If you have selected the Clipboard Service, open the message to import with a text editor. Copy the message content to the clipboard and paste it in the Source Message text box.
-
To start the message import, click Save.
A notification displays that the message has been saved successfully. The message import starts.
-
To check whether the message was successfully imported, select
Transformation > Incoming Messages.
The successfully imported message is displayed in the list of messages on the Incoming Messages page. The message status is Processed.
- If the message cannot be imported, the message status is set to Error on the Import Messages page. To check the error messages, click the Drill down button of the message that cannot be imported. In the detail view, click View Log Entries. In the Log Entries dialog box, the error messages are displayed. You can check the reason why the message could not be imported.