Any manual settings in either ECC or SCM prior to moving transports

[Former Member]

Hi,

We are implementing only the APO GATP with some DP solution along with ECC in IS Retail.

Just wanted to check with the gurus here whether there are any manual settings required in PROD "from an APO perspective only" either in ECC/ SCM "prior" to moving all the transports from Quality to PROD...I was of the opinion that client specific settigns in PROD can also be done once all the transports have been moved from QA.

Please give your inputs.

Thanks in advance.

[Former Member · Accepted solution]

Thanks Rishi & Sreekanth.

If I have understood it correctly:

Defining the Active Version 000 - to be done before moving transports

But with regards to ATP Customizing (Transport vs CIF): can you please elaborate on this - what are the pros n cons in Transporting vs CIF. Have seen that transporting ATP customizing doesn't always give expected results...is it true?

[Former Member · Accepted solution]

Oz

Here are some of the things you might want to do before moving transports. Some of this may be done by your BASIS team -

1. RFC Connectivity (Typically setup by BASIS)

2. Business System Groups (/SAPAPO/C1) & Assignment to Logical Systems (/SAPAPO/C2)

3. Target System & Queue Types (CFC1)

4. RFC Destination assignment to Application Cases (CFC7)

5. Application Server Groups (RZ12 typically setup by BASIS for Parallel Processing)

6. Registering Inbound Queues (SMQR) and Outbound Queues (SMQS) in both ECC and SCM

7. Registering Display programs for Queues (SMQE)

8. Activating CIF Logs (CFC2 in ECC and /SAPAPO/C4 in SCM)

9. Activating ALE Change Pointers (BD61)

10. Activating ALE Change Pointers for Message Type (BD50)

11. Filter & Block Sizes for CIF (CFC3)

12. Change Transfer for Master Data (CFC9)

13. qRFC Alerts (/SAPAPO/CW and /SAPAPO/CQINW)

This is one way to manage ATP Customizing. There could be others -

1. Do ATP Customizing in ECC Dev (if any – if delivered content is not enough)

2. CIF ATP Customizing from ECC Dev to SCM Dev. Add Customizing in SCM

Dev (if necessary)

3. Transport ATP Customizing from ECC Dev to ECC QA. CIF ATP Customizing

from ECC QA to SCM QA.

4. Transport ATP Customizing from SCM Dev to SCM QA

5. Follow similar steps for Production and other environments.

Rishi Menon

[Former Member · Accepted solution]

Thanks Rishi - quite helpful!

[Former Member]

Oz

Ideally you should be doing only and exactly what you already did in QA environment prior to moving transports from Dev environment.

A couple of things to consider - Defining the Active Version 000 and ATP Customizing (Transport vs CIF). 

Rishi Menon

[Former Member]

Hi Rishi,

Thanks for your response...I have joined the project after everything was in QA hence not sure what was done. Any particualar areas in SCM/ ECC for APO/ CIF integration that needs to be done manually before moving transports from QA?

[Former Member]

No other activities required.