Migrate / Customer Opening Balances Upload in Rise with SAP Cloud 2208

[selvinkumar22021988]

Dear All,

Introduction:

This blog will guide you with the steps required for migrating “Customer Opening Balances” into the SAP S/4HANA Cloud 2208.

The SAP S/4HANA Cloud migration cockpit is a tool designed for customers who have just installed SAP S/4HANA Cloud (new implementation scenarios) and want to transfer their business data from SAP or non-SAP software systems. The SAP S/4HANA Cloud migration cockpit has become an essential tool for SAP S/4HANA Cloud data migration, supporting customers during the transition to SAP S/4HANA Cloud . It can be launched using the “Migrate Your Data” app in the Fiori Launchpad (Data Migration Launchpad).

It uses migration objects to identify and transfer the relevant data and, facilitates the migration process by providing predefined migration content and mapping. The SAP S/4HANA Cloud migration cockpit is SAP’s recommended approach for the migration of business data to SAP S/4HANA Cloud.

1. I am SAP S/4 HANA Finance Consultant. I am upload Customer Opening Balance in SAP Cloud Environment.


2. Previously we don’t have any SAP (ECC Version) Standard facilities to upload Customer Opening Balance.


3. Now in Rise with SAP Public Cloud 2208 SAP given the provision to upload Customer Opening Balance One time activity through Migration Cockpit.


4. This blog provides an overview of how to upload Customer Opening Balance in SAP S4 HANA Cloud -2208


5. After migration all Customer Opening Balance (Debit / Credit) amount showing the Customer Balance or FBL5n.

Steps in Customer Opening Balance Upload:

1. Project Creation


2. Download Template (XML File)


3. Upload Template


4. Prepare


5. Mapping Task


6. Simulate


7. Migrate

Fiori Tile Name: Migrate Your Data Migration Cockpit:

Step 1: Click the Tile

 

Step 2: Create Project Name:

Step 3: Create New Project:

Step 4: Select the FI Accounts Customer Open Item:

Step 5: Select the FI Accounts Customer Open Item & Move the Right Side and Click Review:

Step 6: Add the Objects:

Step 7: Click the Create Project:

Step 8: Select The Created Object As Shown Below:

Step 9: Select and Download the Template:

Step 10: Check & fill the Mandatory Filed:

Step 10.1 Xml. file for SAP Format:

Step 11: Click the Upload File:

Step 12: Upload the xml file:

 

Step 13: You Can View The Status in The Upload Files Tab:

Step 14: Click the Prepare:

 

Step 15: Select the Prepare Staging Tables:

Step 16: Select the Mapping Tasks:

Step 17: Mapping the all-Line Item:

Step 18: Do One by one Mapping Confirmed:

Step 19: Ones Mapping is all Confirmed:

Step 20: Select the Simulate:

Step 21: Click the Migrate & System Migrate is Successful:

RESULT:

Now, we have successfully migrated the “Customer Opening Balances” to the SAP S4/HANA Cloud system. In order to see the migrated data in the system, select the Manage Customer Line Item.

Step 22: Balance Upload Check with Manage Customer Line Item:

Step 23: Check the line Item is Successfully Balance Upload:

Conclusion:

From this blog, we have learned how to successfully migrate the Customer Opening Balances to the SAP S4 HANA Cloud System using Migrate Your Data Migration Cockpit tile.

Thanks for reading this blog…

Hope this blog will be useful. If you enjoyed this blog post, please give it a like! If you have questions, feel free to comment.

If you would like to Know More about Finance Related Blogs, Please Follow.

Best & Regards,

Selvin Kumar Sivalingam

[former_member39879]

Hi Selvin,

Very  nice blog

[selvinkumar22021988]

Thank You Sir

[FrankFinkbohner]

Hi Selvin,

Really Nice Blog 🙂
Would be nice if you add how to validate and audit the migrated data via the Data Migration Status app after the data migration or how to use the "Migration Results" view in Migration cockpit to navigate from migrated record to the App.

Best

Frank

[selvinkumar22021988]

Hi Frank,

Thanks for your feedback.

 

[vanhong107]

Hi Expert,

Do you face issue with file has been uploaded and entry has existed but mapping is incorrect, next file can include or not include this field but in mapping task it still contain the field in previous time.

Do you know how to fix it and if possible, can we remove data in staging table after upload?

Thanks and looking for your feedback soon 🙂