SAP BODS landscape setup for data migration

[LeeFung]

          I have a few legacy systems to migrate to SAP ECC on Hana.  Legacy System on Oracle database.   

We are trying to load a few billion (up to 20 billion possible) rows into multiple Z tables in SAP.

My first question is how to set up the BODS landscape?  Is one instance OK for all DEV and QA and PRD purposes?   Or set up BODS DEV, BODS TST, BODS PRD?

My second question is specifically for the scenario of migrating legacy tables into SAP Z tables... is there any tutorial on this setup?

Thanks so much .

[former_member187605 · Accepted solution]

I always set up the same tiers in DS landscape as in ECC. 1-to-1 is easiest to maintain.

For an answer to your 2nd question, refer to (have you ever considered doing a search first before posting?).

[LeeFung]

Dirk: Thanks for your response.

Are you saying :

• BODS DEV --> ECC DEV
• BODS TST --> ECC TST
• BODS PRD --> ECC PRD

We are thinking one BODS box connecting to all 3 ECC systems... I wonder if that is a good idea?

[former_member187605]

That's not a good idea at all. Do you really want your PRD ECC be accessed from within the DEV environment. Talk to your Basis colleagues, I am sure they won't like such approach.

You might want to combine DS DEV and DS TST if you prefer. Saves you one server box. But always keep PRD separate.

[LeeFung]

Thanks a lot. The DFlows and Jobs in the BODS DEV instance... I guess they can be transported to the BODS PRD instance easily just like SAP ECC Transports?   I apologize if this is a stupid question but I should get started on this soon and stop this kind of questions.