Function documentationInterdependent Changes

 

Interdependent changes allow you to create, change, and transfer sales transactions in CRM Enterprise and in the ERP system.

Note Note

  • As soon as you have executed an upgrade for interdependent changes, you can only use this and can no longer use the other data exchange scenarios available up to that point.

  • Interdependent changes are only available for industry and country versions on request.

  • If you use SAP CRM 4.0 <SP04 and SAP R/3 4.7, you cannot use interdependent changes or Data Exchange Scenarios X, Y, and Z.

End of the note.

Prerequisites

  • You use a CRM system that is SAP CRM 4.0 SP04 or higher, and an ERP system that is SAP R/3 4.7 or higher.

  • You have made the following settings, in addition to the general transfer settings (see Data Exchange for Sales Transactions: CRM Enterprise – ERP System):

    • Activation of scenario:

      • Settings in CRM Enterprise: Table SMOFPARSFA

        Key: R3A_SALES

        Parameter name 1: INT_CHANGE_ORDER

        Parameter name 2: <sales document type>, for example TA

        Parameter value 1: A for activating the scenario for interdependent changes for <sales document type>

        Parameter value 2: A for APO activation

      • Settings in the ERP system: Table CRMPAROLTP

        Parameter name: CRM_SCENARIO

        Parameter name 2: INT_CHANGE_ORDER

        Parameter name 3: <sales document type>, for example TA

        Parameter value: A for activating scenario A for <sales document type>

  • You have implemented SAP Note 620139.

  • You have ensured that the documents can be archived in both the ERP system and CRM Enterprise. Otherwise, data inconsistencies can result.

  • You have set up the print function in either CRM Enterprise or the ERP system, but under no circumstances in both systems. Opt for the system you use to run your business, as this is where all current data is found.

You can also find further information in SAP Note 642944.

Features

You can create and change sales orders in both SAP CRM and the ERP system. This means you can also make changes to sales orders and quotations at any time in the CRM Mobile Client. Furthermore, if you use SAP E-Commerce, sales order processing functions are available in the ERP system.

The following availability check scenarios are supported in interdependent changes.

  • Delayed availability check

    You can carry out the availability check after replication of the order to the ERP system. The check can take place in the ERP system or using SAP APO. The confirmed quantities are determined by the ERP system after the transfer, and replicated back to SAP CRM along with the reply.

  • Availability information in SAP CRM against SAP APO

    You simply gain information on availability from SAP APO without actually reserving the quantity. After the transfer to the ERP system, the availability check using SAP APO is performed, and the appropriate quantities are reserved. The confirmed quantities are transferred to SAP CRM.

  • Availability check from SAP CRM in the ERP system

    The availability check from SAP CRM always takes place with the standard item category from ERP Customizing. Any other item category in SAP CRM is not taken into account in the check. This means it is possible that the check may come up with different results, depending on whether the check was carried out from SAP CRM or directly in the ERP system. The confirmations are sent from SAP CRM to the ERP system and are stored there. The system writes the requirements of the ERP system and synchronizes the schedule line numbers in SAP CRM and the ERP system.

    Out of all the data that is relevant for the availability check, you can only change the following in the ERP system when the availability check is active:

    • Order type

    • Sold-to party

    • Product

    • Quantity

    • Account

    • Unit of measurement

    • Requested delivery date

    • Sales organization (at header level)

    If you use SAP ECC 6.0, you can also change the following data:

    • Plant/vendor

    • Ship-to party

    • Batch

    • Item category

    • Requirement rule (fixed date/quantity)

    • Shipping conditions

    • Weighting

    If other data is changed, this can lead to different results.

    You can find more information under Availability Check Using SAP ECC.

Restrictions When Using Interdependent Changes

  • Billing is only possible in the ERP system and not with CRM Billing.

  • The use of rebate conditions is not supported.

  • The use of objects is not supported.

  • The use of configurable materials and structured products is supported with the following restrictions:

    • When you make configuration-relevant changes in the ERP system to an item that was created in SAP CRM, changes to quantity or the configuration in SAP CRM are no longer possible.

    • An item that is relevant for configuration and was created in the ERP system cannot be changed in SAP CRM.

  • Credit approval and rejection, as well as new credit checks, can only take place in one system. This can be either SAP CRM or the ERP system.

  • An availability check from SAP CRM with SAP APO is not supported. Therefore, a rules-based availability check in SAP APO is not possible either. You can only perform an availability check in the ERP system.

  • Maintenance of combined business transactions (quotation and order items in one transaction) is not supported by the ERP system. You can only transfer business transactions that contain either only order items, or only quotation items.