what's the key-factor to integrate Multi-instance R/3 and 1 APO?

[former_member62375]

My customer has some instance R/3. i will propose a style of integrateing Multi-instanace R/3 and 1 APO.

but i don't have any know-how to do it. what should i be careful ? (ex: business group,number range)

good regards

kenji

[Former Member · Accepted solution]

Kenji,

APO allows many R/3s to be connected to a single APO instance. Once configured, APO keeps track internally of the source and destination of each bit of information without any special work by the user.

That being said, APO does NOT like duplicate master records. So, if you have a product ID in one R/3 system 'X' called 'abcd', APO will not let you also freely exchange information about product ID 'abcd' with R/3 system 'Y'. Likewise for locations (which means plants/customers/vendors etc).

There are workarounds, but you should avoid trying to use APO to plan the same master data items in multiple R/3 systems.

Regards,

DB49

[former_member62375 · Accepted solution]

Hi DB49( it's a funny online name!)

thanks for your help.

i know you are right! ( we should avoid master data overlap )

i will add this point in my check-list !

if you have information concerning following case , please let me know.

ex:

1.R/3 A: Sales company ( company code : 123 ) plant : distribution center (location code:DC1)

2.R/3 B: Producting company ( company code:125 ) plant:production plant (location code:PL1)

3.DC1 create SO to DC1's customer. ( Sales order : ABC)

4.DC1 has no stock.

4.run SNP heuristic in APO ( including DC1 and PL1 )

5.DC1 create Procurement request to PL1 in APO.( PR: DEF )

6.PR:DEF is transfered to R/3 A.

7.PL1 create Preqrel.( Preqrel:GHI )

8.Preqrel:GHI is transfered to R/3 B.

is this recognition right?

but my test was unsuccessful on 8 ( Preqrel was not transfered to R/3 B )...

i 'm looking forward to receiving your new info about this.

regards

Kenji.

[Former Member · Accepted solution]

Kenji,

I am told that 'Kenji' means 'twice-as-smart'. I hope you will heed my humble advice.

The issue of which you speak could possibly be solved, but you are now beginning to violate the rule I gave you in my earlier post: Dont try to manage transactions in APO when they are for master data (in this case, Material Master) that is common to two different R/3 systems.

Logically, if you are manufacturing common parts in one R/3 system, but selling them in another R/3 system, you are better off having the two R/3 systems talk between each other (perhaps via IDOCs). Then select ONE of them to talk to APO.

Regards,

DB49

[former_member62375 · Accepted solution]

hi db49!

thanks for your post.

certainly , this problem can be solved by IDOC..(maybe)

but , in additional , it's a question that this following case has been on my mind .

ex:

1. R/3 A and B has different number-range.

in this case, SO's number has a possible that is overlap in APO...

i will verify this case ( of couse i will pay attention to your key-point ) in our test phase!!

regards

kenji

[Former Member]

Hi Kenji,

I am attaching the WIKI Page on CIF which contains the detailed documentation

for your earlier requested points 7) Queue clearance and 😎 sysfail

administration.

https://wiki.sdn.sap.com/wiki/display/SCM/CIF

I hope this will helps you a lot.

Please confirm

Regards

R. Senthil Mareeswaran.

[former_member62375]

hi R. Senthil Mareeswaran!

what a grate job!

i don't know this site ( SDN wikis are really improved ... i 'm amazing!!)

i will check up this site.

regards

kenji

[Former Member]

Hi Kenji,

You can propose integrateing Multi-instanace R/3 and 1 APO to your

customer.

Some of the key areas & challenges to be taken care as follows:

1) Mainitaining integration model without any overlaps

2) Avoid Master data overlaps

3) Maintaining different BSGs

4) qRFC Connections

5) Livecache Setup

6) Delta report iterations

7) Queue clearance

😎 Sysfail monitoring between systems

9) Integration points between R/3 and APO (say like CFC9 transaction)

10) Publication settings for OLTP transfer of data

11) Distribution definition

Regards

R. Senthil Mareeswaran.

[former_member62375]

hi R. Senthil Mareeswaran!

thanks for your greate help.

if you are ok,please let me know in detail about 7) Queue clearance and 😎 Sysfail monitoring between systems.

7) Queue clearance

😎 Sysfail monitoring between systems

->do you have any document to solve this problem?

regards

kenji.

[nitin_thatte]

Hi kenji,

You can easily integrate multiple R/3 systems with one APO.

You should take care while defining distribution definition for publishing planning results to various R/3 systems.

Nitin

[former_member62375]

hi nitin!

thanks for your quick response.

of course distribution definition is really important.

but i don't know how to solve following examples.

ex:

Case

1.R/3 A and R/3 B has same number range.

2.we wanna integrate R/3-A,B and 1 APO.

3.R/3 A transfers Sales-order to APO ( SO number:12345 ).

4.R/3 B transfers Sales-order to APO ( SO number:12345 ).

i think these SO conflicts in APO ( because these SO have the same ATP categoly and order-number ).

is my recognition right ?

if you are ok, please give me some material about this solution.

regards, Kenji