Scribd
Upload
101 views19 pages

Hana Migration SD

Hana_Migration_SD

Uploaded by

amarpattanaik786
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
101 views19 pages

Hana Migration SD

Hana_Migration_SD

Uploaded by

amarpattanaik786
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 19

The individual steps for consultant were as follows:

1. Preparing the Maintenance Planner – BASIS consultant


Analysing the ABAP code using Custom Code Check and adaptation to the S4HANA system
– ABAP consultant
2. Implementing the required SAP Notes – BASIS consultant
Generating the “Pre-Transition Check Result” report – application consultant
3. Preparations in the area of logistics and finance:
a. Customer Vendor Integration
b. Storage Location MRP
c. Material Number Field Extension

Post Migration Step:

1. Activities in the FICO area on the migrated system – FICO consultant


2. Activities in the LOGISTICS area on the migrated system – LOG consultant
 Switch back internal numbering for BP group (BUC2) and external for Customer
account group XDN1
 Define and assign customer number range in direction BP to Customer - Activate
same number

3. Modifying the architecture of the new system – creating a separate database and application
instance – BASIS consultant
4. SAP Gateway configuration – BASIS consultant
5. SAP Fiori configuration – BASIS and application consultants

Pre-check setting up Customer Vendor Integration


The basic configuration of CVI consists of three major steps:
1. Basic Configuration of CVI
2. Customer Integration Configuration
3. Vendor Integration Configuration
4. Dealing with Errors

Tools to run Precheck activities:


1.CVI_PRECHK(T-CODE)
2.CVI_UPGRADE_CHECK_RESOLVE (SE38)
3.PRECHECK_UPGRADATION_REPORT (SE38)
4. MDS_LOAD_COCKPIT (SE38)
1. Basic Configuration of CVI
Use SE38 to run report CVI_FS_CHECK_CUSTOMIZING/ CVI_UPGRADE_CHECK_RESOLVE,
This will give us the idea of the current system configuration about CVI.
Activate Postprocessing Office
Use transaction SPRO to activate the Postprocessing Office, its under the following path:
Cross-Application Components---General Application Functions----Postprocessing Office---Business
Processes---Activate Creation of Postprocessing Orders.

Synchronization Control

Cross-Application Components/Master Data Synchronization-----Synchronization Control

Use transaction SM30 to check view MDSV_CTRL_OPT for queue names for the following objects:

Source Object Target Object Queue Name

BP CUSTOMER MDS_BUPA_CUST

BP VENDOR MDS_BUPA_VEND

CUSTOMER BP MDS_CUST_BUPA

VENDOR BP MDS_VEND_BUPA

Now back to synchronization control preparation, click on queue processing to register the RFC
queues with a * mark at the end of every queue name.
The final results should be look like this;
Synchronization Objects
Cross-Application Components----Master Data Synchronization---Synchronization Control---
Synchronization Control

Activate PPO Requests for Platform Objects in the Dialog


Activate Synchronization Options

Check / Activate Function Modules


Cross-Application Components----SAP Business Partner----Data Distribution---Activate Function
Modules

2. Customer Integration Configuration

Check/Define Number Range for Customer Accounts


Financial Accounting(New)---Accounts Receivable and Accounts Payable---Customer Accounts----
Master Data---Preparations for Creating Customer Master Data
Check/Define Assign Number Ranges to Customer Account Groups

This’s very important, based on the information in this view, we can generally decide which customer
account group should be included during the configuration of CI later on. If the “Number Range”
column is empty, we can assume that customer account group is not activated in the system.
Define BP Roles
Cross Application Component----SAP Business Partner---Business Partner---Basic Settings---
Business Partner Roles
For each entry of the following BP Roles in BP Role Categories, add “BPUS” and “CHAN” with
“Transaction Allowed” Modification Indicator.

FLCU00
FLCU01
FLVN00
FLVN01
Define BP Role for Direction Customer to BP
Cross-Application Components---Master Data Synchronization----Customer/Vendor Integration---
Business Partner Settings---Settings for Customer Integration
The group information was mentioned earlier in section “Check/Define Assign Number Ranges to
Customer Account Groups”

Define Number Assignment for Direction Customer to BP


You may choose the group accordingly.
Define Groupings and Assign Number Ranges
Cross-Application Components---Master Data Synchronization---Customer/Vendor Integration---
Business Partner Settings---Settings for Customer Integration---Field Assignment for Customer
Integration---Assign Keys

Finishing up configurations

Cross-Application Components---Master Data Synchronization---Customer/Vendor Integration---


Business Partner Settings---Settings for Customer Integration---Field Assignment for Customer
Integration---Assign Attributes
Perform all the necessary configuration in this section.
As an example of one of the configurations

3.Run the Synchronize by using Synchronization Cockpit

Transaction Se38 ------ MDS_LOAD_COCKPIT


Check the status, if everything was ok, you should be able to see a green icon in the status field.
Otherwise it’ll tell you what was wrong with the configuration, we’ll deal some of the error later on.
4. Dealing with Errors
Error “Tax Number categories xxx does not exist”

First, let’s maintain the Tax Number categories CN1 and CN5, to do so, use transaction SM30 to
maintain view V_TFKTAXNUMTYPE, copy an existing entry.

Now go to SPRO to Maintain Tax Number Categories, choose create new entries
Cross-Application Components---SAP Business Partner---Business Partner--Tax Numbers
b) Error “address xxx not designated for organizations“

Cross-Application Components---SAP Business Partner---Business Partner---Forms of Address

Finally, we can run the pre-check R_S4_PRE_TRANSITION_CHECKS in client 000 to check if CVI
problem was resolved.
c) Assert Condition violated

This is because of missing industry code in business partners.

We copy all the industry codes of vendor to Business partner configuration.

Double Click on Industry Number Systems and click on create.

User table T016 as base to copy the industry codes from vendor.
Execute Program: FSBP_IND_SECTOR_MAPPING_CHECK

There should not be any industry code in the non-mapped entries for table.

You can execute the program in update mode, it maps to business partners or manually as per
below.
d) Email ID not valid

Because there are spaces and for some @ is missing errors come up. Correct the same in Customer
master data and re-run as below
MDS_LOAD_COCKPIT
Execute
The job is scheduled and you can check the status in monitor tab.

3rd TAB gives list of all the errors.


Once you adjust customer master and correct the email ID, click on individual synchronization. If
there are similar errors you can use Mass synchronization

Finally execute program: CVI_UPGRADE_CHECK_RESOLVE


This will give you the list of vendors and Customers that are not converted.
Sap strongly recommend to go through 2210486,2344034 and 956054.
d) Form of Address 005 not designated for Organizations
Please maintain the data as per below screenshot for this.

e) XXDEFAULT not maintained in address type

Go to SAP Business Partner–>Business Partner–>Basic Setting–>Address Determination–>Define


Transaction and define the business transactions.
and then in the next step Define the address type.
f) Missing link in the CVI table for the same number objects
.
Please follow the instruction of note 2373665 and create a new program
ZCVI_VEND_LINK_CREATE
Execute the above program to fix the inconsistencies in CVI link table and Customer/Vendor master
tables.
Verify CVI_VEND_LINK with LFA1

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy