Postprocessing Customizing Data

Use
The Customizing download is not able to convert all data from the SAP ECC format to the SAP CRM format. Report /SAPCND/RV12N001 carries out a type of postprocessing, and completes the conversion from SAP ECC- to SAP CRM format. It also generates all objects that are required for the condition technique. The converted Customizing is used as a basis. The most current version of the description for report /SAPCND/RV12N001 can be found in the OSS Note 398078.

Activities
Carry out the Customizing download. First step: Conversion of Customizing from SAP ECC- to SAP CRM format with the report /SAPCND/RV12N001. This program carries out the following steps: Corrects Customizing. Calls up the Business Add-In (BADI) /SAPCND/CORR_CUST. This BAdI contains the method AFTER_CORRECTION with which you can make changes to the previously corrected Customizing. Generates objects of the condition technique (for example, condition tables for CRM Enterprise and the CDB). Issues a log (the log is a function of the application log). Second step: Analysis of converted Customizing. Which pricing procedures do I want to support in SAP CRM? Which condition types, access sequences and condition tables must be consistent in CRM? The report PRCC_TRACE_COND_PP is available for the consistency check. Third step: Find out if anything is inconsistent by comparing the IMG settings in SAP ECC with the IMG settings in SAP CRM. Fourth step: Make this all possible with the help of field mapping for the download. (To adopt user-defined fields, see the IMG under Customer Relationship Management Basic Functions Pricing Define Settings for Pricing Adopt User-Defined Fields). Fifth step: Repeat Customizing download and steps 1 to 4 until data is consistent. Sixth step: Delete Customizing that is not required using report /SAPCND/RV12N001. Seventh step: Transport Customizing into the subsequent systems.

Notes:
You can find the most up-to-date help on analyzing errors during data transfer in the OSS System under SAP Composite Note 314542. When exactly do I have to execute report /SAPCND/RV12N001? After each Customizing download. Otherwise never. Not even after upgrade to a new release or after importing a service pack. Which options do I need to set in report /SAPCND/RV12N001, and when? Three phases: Correction of Customizing: Enter CRM, BBP and TAX in the Application field. Enter the values PR and FG in the Usage field. If the fields for application and usage are left empty, values for the application and usage are read out of table CND_MAPC_CNV_UA. Leave the field for the condition table ID blank and switch off all options except for the Customizing conversion. Then execute the report. Another note: The error messages that now appear can be ignored for the moment. As described above, one of the next steps is to find out which of the many records that were downloaded

from SAP ECC are actually required in SAP CRM. Only the required Customizing needs to be error-free. The remainder can be deleted at a later stage. Generation of condition technique objects: The fields for the application, usage and table number can be left empty here. All generation options must be switched on as options (the uppermost of the three blocks) and all options in the middle and lower block must be switched off. Note: The indicator for Customizing conversion must not be switched on. This is not only because conversion has already taken place; since Customizing is still inconsistent, no generation takes place if this indicator is set. Deletion of inconsistent Customizing: Once you have ensured that the Customizing required in CRM is consistent, the indicator for deleting remaining inconsistent Customizing can be set. Do not enter anything in the fields for the application, usage or table number and make sure that all other options are switched off. I have carried out a new Customizing download. Do I need to execute report /SAPCND/RV12N001 again? Yes, the first two steps at least. Do the first two steps really need to be executed again after a new Customizing download? The objects have already been generated once. The Customizing download completely replaces the previously downloaded Customizing. Information that is only available in SAP CRM and was determined during conversion or generation is also lost. The report must be executed in any case with steps one and two. Pricing or condition maintenance is not working properly in my system. You have executed report /SAPCND/RV12N001. After this it was working. The problem reoccurs and you try to execute the report again, but this does not solve the problem. What has gone wrong? Condition tables may be inactive. This does not mean the generated database tables but the condition table object itself. The first generation run probably activated the condition table. A condition table is active if Customizing is consistent and all generated objects are active. You can see if this is the case using table /SAPCND/T681. If the field GESTA has a value of 5 for a condition table, this table is active and is used for pricing and condition maintenance. If the value is not 5 (inactive), the condition table is not available for applications. If the first report run activated the condition table, further generation runs do not bring any new results. The problem is being caused by something else. How can I find out the name of a generated database table in which the data for a condition table was saved? You can use function module /SAPCND/CN_TABLE_NAME_SET to determine the names of the generated objects. Not all objects are database tables.