!--a11y-->
CCR Customizing 
Before you can use the Central Contractor Registration (CCR) interface in the Federal Government solution, some configuration work is required, both in CCR itself and elsewhere in the system.
Prerequisites for the individual customizing activities are described below where appropriate.

You can carry out the activities described below in any order you wish, but you must carry out all of them before doing any CCR processing.
· Maintain Partner Profile (Transaction WE20)
Prerequisite: Partner type “US” (User) must have been created. To do this, go to the Implementation Guide (IMG) and choose SAP NetWeaver ® SAP Web Application Server ® IDoc Interface / Application Enabling (ALE) ® Modelling and Implementing Business Processes ® Partner Profiles ® Process Partner Types.
A partner profile must be maintained to allow for the use of IDOC functionality when creating vendor master data from CCR records. The following configuration steps must be followed as described for the programs to function correctly.
¡ Partner number MUST be 'CCR001' for all programs to work correctly.
¡ Partner type must be 'US'.
a. Make the following entries on the “Post processing: permitted agent” tab:
§ Agent type: User
§ Agent: Whoever is to be responsible for handling any errors arising from the IDOC process.
§ Language: EN (English)
b. Move to the classification tab and set the partner status to “A”.
c. Save your data at this point.
d. Click “Create Inbound Parameter” under the inbound parameter box.
e. In the resulting screen, make the following entries:
Parameter |
Value |
Partner Number |
CCR001 |
Partner Type |
US |
Message Type |
CREMAS |
Process Code |
CRE1 |
Processing by Function Module |
Trigger immediately |
· Cross-System Company Codes
Cross-system company codes must be maintained for all company codes to be used with the CCR Interface. The cross-system company codes are necessary for proper execution of the IDOC generation and creation of vendor master data.
To access the IMG steps for creating and assigning cross-system company codes, choose SAP Netweaver -> SAP Web Application Server -> Application Link Enabling (ALE) -> Modeling and Implementing Business Processes -> Global Organization Units -> Cross-System Company Codes and carry out the following:
a. Cross-System Company Codes (create the cross-system company code here)
b. Assign Cross-System Company Code to chart of accounts
c. Assign Company Code to Cross-System Company Code
The IMG includes documentation with instructions on what to do for each of these activities.
· Access to the Application server on which the system resides
This is necessary because the CCR files (the daily and monthly update files downloaded from CCR's website) must be stored on the application server to work with the CCR Interface programs. Since both file formats are potentially very large, storage on the application server ensures that the files used with the CCR interface will not cause program errors because of hardware limitations.
· When the Central Contractor Registration (CCR) is run, the fields it updates should be displayed in the vendor master change screen, but should not be open for maintenance there.
To specify which fields are processed in this way, go to the Public Sector Management section of the IMG and choose Functions for US Federal Government ® Integration ® Central Contractor Registration ® Maintain Vendor Master Display Fields for CCR.
· You must also run Business Add-In (BAdI) FMFG_CCRVNDORMIGRATE, which maps the CCR fields to the corresponding vendor master fields. Sample code is available.
· To access the BAdI, choose Functions for US Federal Government ® Integration ® Central Contractor Registration ® Business Add-Ins for CCR ® BAdI: Move CCR Data to IDoc Segment Fields.
You can now run the programs described in CCR Processing.
