Guide - IOM 4.1 Migration of Business Configuration

Table of Contents


Product Version

4.1

Product To Version

4.1
Status

1 Debtor Management: Split SalesOrders / PurchaseOrders export configuration

Up until IOM 4.0.0 the export of SalesOrders/PurchaseOrders XML files for debtor management systems has been configured via a single configuration in CommunicationPartnerDO. In order to allow a more flexible configuration, this has been separated into three different configurations:

  1. Invoice Export - "SalesOrders" format: This continues to work with the old configuration.
  2. PurchaseOrders XML "on dispatch" - covered by the new transmission type "SEND_PURCHASE_ORDER_DISPATCH". In order to use it, create a CommunicationPartnerDO pointing to CommunicationDO with key = XML###MESSAGE_FILE_SENDER_BEAN###SEND_PURCHASE_ORDER_DISPATCH
  3. PurchaseOrders XML "on return" - covered by the new transmission type "SEND_PURCHASE_ORDER_RETURN". In order to use it, create a CommunicationPartnerDO pointing to CommunicationDO with key = XML###MESSAGE_FILE_SENDER_BEAN###SEND_PURCHASE_ORDER_RETURN

For detailed configuration examples please refer to Reference - IOM ImpEx Interfaces.

2 RMA Export - Split by Supplier

From now on the out-of-the-box (XML) export for RMA transmissions will only include positions that were assigned to the supplier referenced in the transmission configuration.

Example:

  • CommunicationPartnerDO is configured - sendingPartnerReferrer = SHOP, receivingPartnerReferrer = SUPPLIER_X. The export will filter out all ReturnAnnouncementPosDOs that do not belong to order positions assigned to SUPPLIER_X.
  • CommunicationPartnerDO is configured - sendingPartnerReferrer = SHOP, receivingPartnerReferrer = (null). The export will not be filtered - XML contains all ReturnAnnouncementPosDOs.

Note

This change only applies to the mapping itself - the creation of ReturnAnnouncementTransmissionDOs (RATDO) has not been changed. IOM will create a RATDO for every configured CommunicationPartnerDO, independently of the SupplierDOs that are actually assigned to order positions.


Example:

  • Order contains positions for SUPPLIER_A only
  • CommunicationPartnerDOs exist for receivingPartnerReferrer = SUPPLIER_A and SUPPLIER_B
  • After creating a ReturnAnnouncementDO for any position, IOM will create two RATDOs - for SUPPLIER_A and SUPPLIER_B!

The export for SUPPLIER_B will fail with an error in this case (no matching positions = empty position list). To prevent this, implement and configure a DecisionBean method 

isExecutionRequired(ReturnAnnouncementDO, CommunicationPartnerDO)

that only triggers the creation of RATDOs for ReturnAnnouncementDOs that reference order positions for that particular CommunicationPartner / Supplier.

Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

Customer Support
Knowledge Base
Product Resources
Tickets