Show TOC

 Prerequisites for the Product Transport

Prerequisites

General Prerequisites

The following general prerequisites must be met before you can perform a product transport:

  • You must set up the target destinations (logical systems) used for the product transport in Customizing. See the Customizing section.

  • The product models must contain the same categories, hierarchies and product roles.

  • The users defined in the RFC connection must have the corresponding authorizations to create products in the target system.

  • Authorization to download or export product data must be available in the source system (authorization object CRM_IU_PDL).

  • If you are using BRFplus rules in the product model, you must install the Add-On SAP NetWeaver Decision Service Management (SAP NW DSM). You must also set up a managed system for each target destination. For more information about these settings, see the section Import Transaction in the Target System.

  • You must activate the business function Product Transport for Utilities (CRM_UT_PROD_TRANS) in the source and target system(s).

Product-Specific Prerequisites

The following product-related prerequisites must be met before you can perform a product transport:

  • The product must have a status that allows it to be transported. These are:

    • Active for Testing

    • Released

  • Most product-specific checks to establish whether a transport can be performed take place before making the change to a status that can be transported. The system for example checks whether the BRFplus rules used can be activated without errors occurring.

  • A corresponding target destination must be predefined in Customizing for each current status that can be transported.

  • The configuration attributes used in the simplified configuration must exist with an identical definition in both systems in Customizing. You make the corresponding settings for this in Customizing for Customer Relationship Management under Start of the navigation path Industry-Specific Solutions Next navigation step Utilities Industry Next navigation step Transactions Next navigation step Simplified Configuration Next navigation step Maintain Simplified Configuration Attributes End of the navigation path (transaction CRM_ISU_CONFIG).

Transport Sequence

  • If you are using product modules or reference products as components for another product, product module or product determination object (PDO) or product structuring object (PSO), these product modules or reference products must already be available in the target system. They must be transported separately in the version used in a preceding step.

  • Component elements (products) in hierarchical products (product determination object PDO/utilities package product) or from product proposals from product structuring objects must also already be available in the target system (not version-specific). The assignment in the product hierarchy is made in the target systems and may be based on a different product version to the one in the source system.

Note Note

Products that contain errors and products with the status In Process or Obsolete cannot be transported.

You can only transport the most recent version of a product.

End of the note.
Upload-Relevant Data

  • Set types for services

    • Product header data (COMM_PRODUCT)

    • Short texts (COMM_PR_SHTEXT)

    • Long texts (COMM_PR_LGTEXT)

    • Units of measure (COMM_PR_UNIT)

    • Tax data (CRMM_PR_TAX)

    • Transaction parameters (CRMM_PR_BTR)

    • Sales data for order (CRMM_PR_SALESA)

    • Sales data for pricing (CRMM_PR_SALESG)

  • Set types for products for the utilities industry

    For the complete list, see the documentation for the transaction CRM_ISU_PRODHIER.

Constraints

Only actual product data is transferred during the transport. Additional data such as classifications, relationships or conditions is not transferred. The sales status is also never transported.