03-07-2008 11:33 AM
03-10-2008 2:37 PM
Hi sandeep
followingR/3 Retail Interface
Customizing Guide
This customizing guide describes all necessary settings in the two SAP systems to enable data exchange and perform the scenario shown to the left.
This customizing guide was written for the IDES landscapes and therefore the names of systems, customers, vendors or organizational data are only examples. It is assumed that both systems are configured to enable business flow from purchasing to financial accounting.
The settings are made as simple as possible to ease the setup. As soon as the interface works properly more complex settings can be done.
For the same reason some features that are described in the official documents on the AFS-Retail-Interface have not been set in place:
1) Bills of material process and the corresponding partner profile settings.
2) Workflow that would inform the user in the retail system that a new article has been created and needs to be listed.
Menu path / TA
Settings in Retail system
Settings in AFS system
IDES Retail system DHR, (4.7) IDES AFS system DH6 (4.6d)
System Settings / Customizing
The distribution and communication is based on Application Link Enabling (ALE) and IDoc interface technology. A Remote Function Call (RFC) connection is needed to establish the general possibility of data exchange between the two systems.
The following two steps have only to be done, if the connection is established for two empty systems. In an existing landscape like IDES no new logical systems have to be defined. In the following step Assigne Client to Logical System creates a client in Retail and AFS which is not needed in the following procedure!
Define logical System
Retail: IMG SAP Web Appl. Server
AFS: IMG Basis Components
ALE Sending and receiving systems Logical System Define logical System Log. System Name
RET_00_760 Own system
Log. System Name
AFS_00_781 R/3 AFS
Define Target systems for RFC Calls
Retail: IMG SAP Web Appl. Server
AFS: IMG Basis Components Sending and Receiving Systems Systems in Network Define Target systems for RFC Calls
(SM59) R3-connection
Destination: DH6
Description: Interface AFS-Retail
Target host: Iwdf9459 / 64
Logon:
Language: En ,Client: 781, User: IBS_RFC; Password
R3-connection
Destination: DHR
Description: Interface AFS-Retail
Target host: iwdf9454 / 53
Logon:
Language: En, Client: 760, User: IBS_RFC, Password
A port is the name of the channel by which the SAP system exchanges electronic data with an external system. For this scenario transactional RFC port s are created.
Define Ports
Retail: IMG SAP Web Appl. Server
AFS: IMG Basis Components Sending and Receiving Systems Systems in Network Asynchronous Processing Assigning Ports Define Ports
(WE21) Transactional RFC
own port name: to AFS
Description: Port to AFS System
RFC destination: DH6 Transactional RFC
own port name: to Retail
Description: Port to Retail System
RFC destination: DH6
A distribution model describes the Applicaton Link Enabling (ALE) message flow between logical systems. The relationships between logical systems, message types, BAPIs and filters are defined in the distribution model. Applications and the ALE layer use the distribution model to determine receivers and to control the data distribution. The distribution model is used in this scenario to enable the distribution of master data (material / article master, price conditions, dimensions) between AFS and Retail.
The IDoc WMERCAT is used to send information about merchandise category and characteristic from Retail to AFS where this data will be matched with dimension and grid data.
Maintain Distribution Model and Distribute Views
Retail: IMG SAP Web Appl. Server ALE Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views
AFS: IMG Basis Components Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views
(BD64) Press button
Module AFS_Retail_ARTMAS_Idoc_INPUT
Type F
Basic type ARTMAS03
Message type ARTMAS
Direction 2
Thanks
Amit Shivhare
Edited by: Amit Shivhare on Mar 11, 2008 4:54 AM
03-07-2008 11:37 AM
Hi Sandeep
The distribution and communication is based on Application Link Enabling (ALE) and IDoc interface technology. A Remote Function Call (RFC) connection is needed to establish the general possibility of data exchange between the two systems
Thanks
Amit Shivhare
03-10-2008 5:46 AM
Hello Sandeep,
This link talks about AFS Retail interface in detail. Have a look at this. Any further queries, feel free to ask
http://help.sap.com/saphelp_47x200/helpdata/en/20/a7ac36694e7f45e10000009b38f839/frameset.htm
Regards
Sudha
Edited by: Sudha Naik on Mar 10, 2008 6:47 AM
03-10-2008 9:33 AM
Hi, in SAP Retail, the strength lies in distribution, where as in SAP AFS , the strength lies on Color,Size and Product Specification (Manufacturing of Products).Based on this AFS has supplying role for the retail companies, and the relationship is Customer-Supplier Relationship.
03-10-2008 2:37 PM
Hi sandeep
followingR/3 Retail Interface
Customizing Guide
This customizing guide describes all necessary settings in the two SAP systems to enable data exchange and perform the scenario shown to the left.
This customizing guide was written for the IDES landscapes and therefore the names of systems, customers, vendors or organizational data are only examples. It is assumed that both systems are configured to enable business flow from purchasing to financial accounting.
The settings are made as simple as possible to ease the setup. As soon as the interface works properly more complex settings can be done.
For the same reason some features that are described in the official documents on the AFS-Retail-Interface have not been set in place:
1) Bills of material process and the corresponding partner profile settings.
2) Workflow that would inform the user in the retail system that a new article has been created and needs to be listed.
Menu path / TA
Settings in Retail system
Settings in AFS system
IDES Retail system DHR, (4.7) IDES AFS system DH6 (4.6d)
System Settings / Customizing
The distribution and communication is based on Application Link Enabling (ALE) and IDoc interface technology. A Remote Function Call (RFC) connection is needed to establish the general possibility of data exchange between the two systems.
The following two steps have only to be done, if the connection is established for two empty systems. In an existing landscape like IDES no new logical systems have to be defined. In the following step Assigne Client to Logical System creates a client in Retail and AFS which is not needed in the following procedure!
Define logical System
Retail: IMG SAP Web Appl. Server
AFS: IMG Basis Components
ALE Sending and receiving systems Logical System Define logical System Log. System Name
RET_00_760 Own system
Log. System Name
AFS_00_781 R/3 AFS
Define Target systems for RFC Calls
Retail: IMG SAP Web Appl. Server
AFS: IMG Basis Components Sending and Receiving Systems Systems in Network Define Target systems for RFC Calls
(SM59) R3-connection
Destination: DH6
Description: Interface AFS-Retail
Target host: Iwdf9459 / 64
Logon:
Language: En ,Client: 781, User: IBS_RFC; Password
R3-connection
Destination: DHR
Description: Interface AFS-Retail
Target host: iwdf9454 / 53
Logon:
Language: En, Client: 760, User: IBS_RFC, Password
A port is the name of the channel by which the SAP system exchanges electronic data with an external system. For this scenario transactional RFC port s are created.
Define Ports
Retail: IMG SAP Web Appl. Server
AFS: IMG Basis Components Sending and Receiving Systems Systems in Network Asynchronous Processing Assigning Ports Define Ports
(WE21) Transactional RFC
own port name: to AFS
Description: Port to AFS System
RFC destination: DH6 Transactional RFC
own port name: to Retail
Description: Port to Retail System
RFC destination: DH6
A distribution model describes the Applicaton Link Enabling (ALE) message flow between logical systems. The relationships between logical systems, message types, BAPIs and filters are defined in the distribution model. Applications and the ALE layer use the distribution model to determine receivers and to control the data distribution. The distribution model is used in this scenario to enable the distribution of master data (material / article master, price conditions, dimensions) between AFS and Retail.
The IDoc WMERCAT is used to send information about merchandise category and characteristic from Retail to AFS where this data will be matched with dimension and grid data.
Maintain Distribution Model and Distribute Views
Retail: IMG SAP Web Appl. Server ALE Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views
AFS: IMG Basis Components Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views
(BD64) Press button
Module AFS_Retail_ARTMAS_Idoc_INPUT
Type F
Basic type ARTMAS03
Message type ARTMAS
Direction 2
Thanks
Amit Shivhare
Edited by: Amit Shivhare on Mar 11, 2008 4:54 AM
03-13-2008 9:42 AM
04-07-2008 10:41 AM
hi sandeep/ amit,
good question by sandeep and fantastic answer by amit,
regards
santosh jaiswal
04-07-2008 10:46 AM
hi sandeep/ amit,
good question by sandeep and fantastic answer by amit,
both are genious.
regards
santosh jaiswal
04-09-2008 3:59 PM