Show TOC

ProcedureTransferring Conditions from SAP CRM to SAP ERP

 

This procedure describes how to configure conditions for trade promotion management (TPM), campaign management, and account planning in SAP CRM and SAP ERP integrated scenario. This configuration applies to condition generation and manual creation of conditions. The procedure also describes how to transfer the conditions that are created in SAP CRM to SAP ERP.

Note Note

Make the following settings in the SAP Easy Access screen.

End of the note.

Prerequisites

You have completed the settings in SAP ERP in Customizing for Sales and Distribution under:

  •   Basic Functions   Pricing  

    You have made the settings for pricing conditions here.

  •   Billing   Rebate Processing  

    You have made the settings for rebates here.

  •   Basic Functions   Free Goods  

    You have made the settings for free goods for Marketing planning here.

  •   Integration with Other mySAP.com Components   Customer Relationship Management   Basic Functions   Campaign Determination  

    You have made the settings for campaign determination conditions for Marketing planning.

Procedure

Transfer Condition Customizing from SAP ERP to SAP CRM

In your initial Customizing download, select DNL_CUST_CNDALL. For all subsequent downloads, use the filters available to select only what is required to avoid overwriting existing Customizing data.

  1. In SAP CRM, start the download in Start Initial Load (transaction R3AS) and specify the Load Object (for example, DNL_CUST_CNDALL) and the Source Site (Sender) (for example, QWCCLNT555).

    Select a source site name for each table or structure you want to download.

  2. Save.

  3. In Variant Attributes, specify what you want for the values of the fields that appear.

  4. Click Regenerate Filter.

  5. Save.

  6. When your download is finished, remove the filters for any future downloads.

  7. Ensure the Inactive checkbox is not set.

Note Note

MNTCNT is the table in SAP ERP that corresponds to the entries in SAP ERP in Customizing for Integration with Other mySAP.com Components under   Customer Relationship Management   Basic Functions   Data Exchange Conditions  .

T681* / T682* / T683* / and so on are the condition tables in SAP ERP that correspond to the CUS* condition tables in SAP CRM.

End of the note.
Monitor the Download

To monitor the progress of the Customizing download, go to Monitor Objects (transaction R3AM1) and specify the load object (for example, DNL_CUST_CNDALL).

Initially, the process has the status Running. If, after a few minutes, the figure in the Block column remains at zero (0), the process has errors. Double-check the remote function call (RFC) connections from SAP CRM to SAP ERP and from SAP ERP to SAP CRM for the appropriate clients.

If the transfer does not work, here is a list of possible problems you may face and how to resolve them:

  • When you enter a specific condition type in Customizing for Marketing condition generation or when you try to generate conditions on a trade spend line that leads to a specific condition type, the following error message is displayed: There are tables for condition type XXXX but they cannot be maintained.

    This means that table MNTCNT in SAP ERP was not maintained correctly at the time of the download. The entries in table MNTCNT should be transferred to /SAPCND/T681M (SAP CRM client-specific table).

    Note Note

    In Maintain Table Views: Initial Screen (transaction sm30), check the SAP CRM cross-client tables /SAPCND/T681 and /SAPCND/T681M.

    End of the note.

  • Although the Customizing entries have been transferred successfully, they have not yet been activated.

    1. Correct any errors in the table and transfer the Customizing again. It may be that the condition mapping table in SAP CRM is not maintained correctly.

    2. Go to Maintain Table Views: Initial Screen (transaction sm30) and call up the mapping tables CND_MAPC_CNV_FLM (standard Customizing delivery) and CND_MAPM_CNV_FLM (customer delivery).

    3. Check the mapping for all of the tables' fields is complete (except for those fields that have the same name in both SAP ERP and SAP CRM).

  • Condition types from SAP ERP link to access sequences that do not exist anymore in SAP CRM. However, new access sequences appeared in SAP CRM.

    Cross-client Customizing including access sequences and/or condition tables was already downloaded and it overwrote the original access sequences that were in SAP CRM. Errors occur only if the original access sequences were not part of the download. Since the condition types are client-dependent, they were not affected by the download, so they now point to access sequences that do not exist anymore.

    You cannot manually modify SAP ERP condition types in SAP CRM to link them to the new access sequences. This is because the SAP ERP condition types are read-only in SAP CRM. Nor can you create new SAP CRM condition types that link to the new access sequences.

    If the new access sequences can be used in Marketing, you can modify the condition types in SAP ERP to link to the new access sequences. Download the client-dependant Customizing with tables MNTCNT and T685*. Do this in the client-dependant system. If the new access sequences cannot be used by Marketing, download the cross-client Customizing download with tables MNTCNT, T681*, T682*, and TMC1*. Do this in the cross-client system.

Initial Transfer of Conditions

  1. In SAP CRM, go to Adapter Object Overview (transaction R3AC5).

  2. Define adapter objects for condition tables in SAP CRM.

    You can define one adapter object for each condition table or for several condition tables.

    Note Note

    For more information on the adapter framework and adapter object management, see the SAP Library, by choosing   Help   Application Help   in the SAP Easy Access screen.

    End of the note.

  3. Go to Start Initial Load transaction (R3AS) and start the initial load of data for trade promotions.

    Enter the:

    1. Object name

    2. CRM Server name as the Source Site (Sender)

    3. SAP ERP name as the Destination Site (Receiver)

Transfer of Condition Updates

  1. In SAP CRM, go to Middleware Object Navigator (transaction CMWMON).

  2. Select Subscription and enter the relevant object.

  3. Select Site and check that the R/3 entry contains the following subscriptions:

    • Agreements

    • Conditions

    Check that the object classes correspond to the adapter objects you defined in Adapter Object Overview (transaction R3AC5).

    The following object classes have to be there:

    • AGREEMENTS

    • CONDITIONS

    The object classes have to be linked to the right destination (for example, QWCCLNT555 for SAP CRM 5.1).

  4. Ensure the object classes correspond to the adapter objects you defined in transaction Adapter Object Overview (R3AC5).

Note Note

Ensure you have activated conditions in SAP ERP once you are ready to use trade promotion condition records in SAP ERP sales orders.

End of the note.