Wednesday, September 24, 2008

RFC Link Between SAP R/3 and SAP APO

RFC Link Between SAP R/3 and SAP APO
The RFC link between R/3 and APO is a .normal. RFC link. The exchange
of data takes place without using IDocs.
The corresponding Customizing settings in the R/3 are under: Web
Application Server → Application Link Enabling (ALE) (R/3 transaction
SALE), and for APO, similarly, under APO Customizing: R/3 Basis
Customizing → Application Link Enabling (ALE) (APO transaction SALE).
Define RFC Destinations
The RFC links run in both systems under the title .R/3 links.; as far as the
basis is concerned, an SAPAPO System is identical to a R/3 Enterprise.
The User specified in the RFC link should be a .normal. dialog user
(officially recommended and supported by SAP; the dialog abilities of the
user are necessary for the APO-ATP integration in an R/3 sales order).
The authorization profile SAP_ALL should be assigned to the user (in
other words, there is no special authorization profile for this user). Logon
usually takes place in the language that is specified in the RFC connection
(also for the ATP check).
For RFC links, if a transfer error occurs due to network errors you can set
new transfer attempts to start automatically in the definition of RFC link
under Destination → TRFC Destinations.
Determining Target System and Maintaining APO Release
Specifying the SAP APO target system in the settings of the CIF (R/3
transaction CFC1) means that the relevant SAP R/3 Enterprise is
recognized as an SAP APO System. This entry and the maintenance of the
APO release are required for a successful CIF data transfer. The operation
mode behind the system is not maintained manually, but is assigned by
the system.
The APO Release must be known to the system, as some points in the logic
of the CIF transfer changed between APO Release 2.0 and 3.0/3.1, for
example, the transfer of PPMs.
Several SAP APO target systems can be specified for integrating an R/3
Enterprise with several SAP APO Systems. In the integration model for
the data transfer from R/3 to APO, the relevant target system is clearly
specified.
The target system for the retransfer of planning results from APO
is determined in APO according to publication type, for example,
external procurement or in-house production, and location under APO
Customizing: Advanced Planner and Optimizer (APO) → Basis Settings →
Integration → Publication → Maintain Distribution Definition. The retransfer
is set in transaction /SAPAPO/C4: Tools → APO Administration →
Integration → Settings → User Settings. For SNP planning results, SNP
Customizing defines how the retransfer is to take place.
Hint: Some settings (SM59 and CFC1) can also be called up
centrally in the R/3, using the CIF Menu. You can access the
CIF Menu using the transaction CIF with /n, after you leave the
Easy Access Menu. However, note that new transactions are not
included in the CIF menu. It is also possible to use the Easy Access
Menu.
Business System Group (1)
Each system must be assigned to a BSG; at least one is necessary in every
case. If there is not a risk of ambiguity, all systems are assigned to the
same BSG.
This and the following presentations show that one SAP APO System is
connected to several R/3 Enterprises, where the same material number
indicates different materials in different systems.
The opposite of this, where the same material has different material
numbers in different R/3 Enterprises, is discussed in the appendix.
Business System Group (2)
The SAP APO System is also to be assigned to a BSG. Development
recommend that you assign the APO System to the BSG, then the data
does not need to be renamed.
Business System Group (3)
For the resources, a BADI, a new technology, is used instead of a customer
exit.
Renaming PPMs is usually not necessary: The product number linked to
the PPMs is renamed. The PPMs in theAPO System are then also uniquely
activated.
Business System Group (4)
The original R/3 names of, for example, an APO product or location, are
apparent in APO: They are specified in the product or location master as
an external material number or location. This information can be found in
the APO tables /SAPAPO/MATMAP and /SAPAPO/LOCMAP can be
displayed with APO transaction SE16.
Outbound and Inbound Queues
Since PI2001.2, there is an option available where you can choose between
outbound and inbound queues in integration. Previously, you could only
process through outbound queues, which will be the standard case for
this course too, at first.
Monitoring and error handling differentiate slightly for outbound and
inbound queues. These are the only differences for this setting in the
application.

1 comment:

Dan Cristian said...

Hello,

Your post is interesting and useful; thank you for it. You might want nonetheless to amend your statement regarding SAP_ALL profile to be added to the RFC user. For this you can make reference to SAP SCM 5.0 Component Security Guide and to SAP note 727839 (Authorization role for the SAP SCM - SAP R/3 integration). You will find quite different recommandations there.

With regards,
Dan Cristian Georgescu
SAP NW 7