This action might not be possible to undo. Are you sure you want to continue?
Sudeep nag Vemulapati. Outbound Process Steps: Client 800. Step1: LOGON to 800: Execute Transaction Code: SALE Under Basic Settings Logical Systems Define Logical Systems Execute.
Click New Entries.
Enter the Logical Systems Name and Description LOGICAL SYTEM NAME (DESCRIPTION) SYSLOG800 LOGICAL SYSTEM FOR CLIENT 800 SYSLOG810 LOGICAL SYSTEM FOR CLIENT 810 SAVE. NOTE: Here in this example we are working with two clients (800 and 810) of the same server so that the logical systems are created automatically in all the clients, else the same should be created in the receiver client 810 in the same way.
Will open a pop-up : Prompt for workbench request. Just click on the create button to create the request number automatically Click Enter. Press F3/Click on Back to navigate to the first screen of SALE. Under Basic Settings Logical Systems Assign Logical Systems Execute. SYSLOG800 is assigned to client 800. SYSLOG810 is assigned to client 810. As these are cross clients, we can assign the client 810 in client 800.
e. . SYSLOG800.Select the Client 800 and double click on it to assign logical systems by providing the client details. Provide the description to the client 800 (SENDING SYSTEM) and assign the Logical System as created i.
The called program is executed locally on the remote computer using the remote computer’s environment.Repeat the same procedure in the receiver system/client 810 to link the client 810 to the logical system SYSLOG810. 5. Remote function call is one of the great achievements of TCP/IP networks. Every computer within the network can accept an RFC-call and decides whether it wants to execute the request. 4. It is just like stepping over to the remote computer. The called program can be run under a completely different operation system. Every modern FTP server implementation includes the RFC calling feature. consuming the caller’s resources of CPU. In the RFC destination. CPU and data storage. The called program needs not to be present on the calling computer. The remote computer decides whether to fulfill the request and execute the program. The calling program task waits meanwhile for the called program to terminate. When the program is called. execute the transaction code SM59 . Till now participating clients are named and assigned to the logical systems. An RFC calls the program on the remote computer. memory and disk. In the Client 800. When the RFC program terminates. we provide IP address and the logon details of the receiver client. 2. the code will be transported via the network to the calling computer workstation and executed on the calling computer. A classical network server stores the program code in a central location. Step2: Maintain RFC (Remote Function Call) destinations: A Remote Function Call enables a computer to execute a program on another computer. it returns result values if applicable. 7. 6. typing in the program command line with all parameters and waiting for the result to be reported back to the calling computer. so you can call a WINDOWS program from UNIX and vice versa. Every manipulation done by the called program is effective in the same way as if the program had started on the remote system. It calls the program on a remote computer and specify parameters if and as necessary. 3. The calling computer does not provide any resources other than the parameters specified with the call. Functions of RFC: 1.
Go to Logon/Security tab and provide logon details of the destination. Provide RFC Destination: SYSLOG810.Select R/3 Connections and click on Create button. Language: EN Client: 810 User: SAP USER Password: ******* . Connection Type: 3 (for ABAP Connection) & Description.
System name Target Host: gcecc62.e. System Number: 00 (check the SAP logon pad for system number) .Then go Technical Settings tab and Provide Target Host i.
SAVE and continue with the information: User can be used for remote logon in target system. Client 810 . Testing the RFC Destination: Click on Remote logon Button from the same screen and make sure that you are able to logon to the receiver’s system i.e.
Repeat the RFC destination from receiver and sender as shown in the below screen shots as our example is based on 2 way communication. .
.SAVE COMMUNICATION. Execute the Transaction Code: BD 64 and click on Edit. Step 3: Maintain the Distribution Model.
Select the Model View Created and click on Add Message Type button. Note: Distribution Model acts as a bag to carry the list of receiver details for any message type and any receiver from the sending system i. SYSLOG800. Technical Name: SYSLOGMDL SAVE. Sender: Receiver: Message Type: SYSLOG800 SYSLOG810. Receiver and Message Type Details. Description: Model View to Distribute MATMAS data. .e. MATMAS.Click on Create Model View and provide the Technical Name for Model View and short description. Provide Sender.
. MATMAS. Sender: Receiver: Message Type: SYSLOG810 SYSLOG800. Also repeat the same for the client 810 as it is a two way communication. Repeat the Add Message Type steps for each message type to be transferred. Receiver and Message Type Details. Select the Model View Created and click on Add Message Type button. Provide Sender.SAVE.
select the Model View Created and go to Environment (in the menu bar) and click on Generate Partner Profile to create port for client 800.In the same screen of Client 800 i. (Target Logical System) . Provide Model View Created: SYSLOGMDL and Partner System: SYSLOG810. Distribute Model changed.e.
Click on F3 (Back) Click on F3 (Back) . Check whether the port number created successfully or not.Execute to create Port for client 810.
Select the Model View Customized and go to Edit (Menu Bar) Model View Click on Distribute. This step is to make the Model View available to client 810. .
Select Client 810 and execute the Transaction Code: BD82 for creating Partner Profile. Select the Logical System SYSLOG810 and click Enter Provide Model View Created: SYSLOGMDL and the Partner System: SYSLOG800 .
. Step: 4 (To activate Message Type) Select Client 800 and execute the Transaction Code : BD50 to activate Message Type.Execute to create port for client 800. Check whether the port number created successfully or not.
.Select the Message Type: MATMAS and enable active. SAVE. Select BD 52 (For selecting the fields to transfer from client 800 to client 810) Click Enter Select the required fields to transfer.
Save. Execute the Transaction: MM01 (Material master application) Provide Material: CHANGEPOINTERS3 .Click Enter Enable the Change pointers to activate generally.
Select Basic Data 1 and Basic Data 2 .Industry Sector: Mechanical Engineer Material Type: Raw Material. Click Enter.
Base Unit of Measure: KG Gross Weight: 1000 Net Weight: 1000 Weight Unit: KG SAVE the raw material data. The receiving systems for the specified message type are determined from the customer distribution model.Provide Description for change pointers and Provide Units. It then sends them to the receiving system and flags the change pointers as processed in respect of the specified message type. Description: CHANGEPOINTERS_MATERIAL. RBDMIDOC: RBDMIDOC is a standard ABAP report available within the SAP system which creates IDOC’s from the change pointers for the specified message type. Select ABAP Editor by executing the Transaction: SE38 Execute RBDMIDOC. .
Data records. . Execute the Transaction Code: WE05/WE02 to check the IDOC Number generated.Provide Message Type: MATMAS. Execute. and the Status of IDOC.
If the status codes are 01 and 03 IDOC created successfully. In the status record. If the status code is 29 IDOC created with errors. if the status codes are 50 and 53 IDOC processed successfully. If the status code is 51 IDOC processed with errors. . Select the client 810 and execute the transaction: WE05/WE02 to check whether the IDOC processes successfully or not. Check the Status Record.Execute.
.To reprocess the IDOC in Inbound System (Client 810) Execute the transaction WE19 Provide IDOC number: 77004 Execute.
Click on Inbound function Module and provide the function module name Function Module: IDOC_INPUT_MATMAS01. Check the IDOC Number processed by the function IDOC_INPUT_MATMAS01 . Choose the call transaction processing as per your convenience and click enter.
Execute the Transaction Code: MM02 and check the raw material data transferred to client 810.Execute the Transaction Code: WE05/WE02 to check the reprocessed IDOC. .