18th MARCH

WE31 : SEGMENT CREATION

WE30 : IDOC CREATION
WE81 : LOGICAL MESSAGES CREATION
WE82 : ASSIGN LOGICAL MESSAGES TO THE IDOC.

Segments : is used in IDOC to Specify the Structure of IDOC.

1) Customer data
2) Material As Inquiry.

At the time of Idoc Creation . what is difference between create as Copy and Create
Successor of ?

if we select Create as copy Sap Search the existing idoc from SAP version 4.x, if found
abaper can attach existing idoc segments into current IDOC.

if we select Create Successor Of is the option used to select existing idoc's from the
version 3.x or 2.x.

Logical Messages:
Are used in SAP to attach IDOC existing in DataBase layer of the current R/3
system into partner profile of Application Server. If the Partner profiles are added with
IDOC's can send data from current system To remote System or remote System to current
System with help of Inbound and OutBound Process.
These can give the status idoc while data Transportation between The network.

Navigations to create Idoc's

1) Creating Segments.
WE31 -> NAME THE SEGMENT ( ZSEG9301) -> CREATE -> ENTER SHORT
TEXT -> SPECIFY FIELD NAME -> DATA ELEMENT -> SELECT ISO STANDARD
CHECK BOX -> [ Repeat the same step for adding fields for the segments ] -> save the
object .
Note : create this type of segments for the requred data to be transported.

2) Create IDOC
WE30 -> NAME THE IDOC(ZIDOC930) -> CREATE -> Open an interface select ->
create new -> short description -> continue -> Open LPS with IDOC Name -> select the
IDOC -> click on create Segment ( from application toolbar ) ->
Opens Another interface

seg type : zseg9301

checkbox ( mandatory segment )[ if master segment select it]
minimum number : 1
max number :1 ( for mandatory )
minimum number says one transaction
max number of records number of rows can be added for the idoc.
-> click on continue ( Segment is added to IDOC).

Repeate the same step to add other segments into idoc.

-> save the idoc -> come back.

Create Logical Messages:

WE81 -> change mode of the screen -> click on new entries -> Enter Message
Type ( ZLOGMSG930) -> Enter short text -> save the Entries.

IDOC's can be created as Local Object But can't be used for data Transfering.

Assign Logical Message with IDOC

WE82 -> CHANGE MODE -> New Entries -> Name the message Type ( Logical
Message Name ) [ zlogmsg930] -> enter basic type ( idoc Name ) -> Release version
( 620) [ for 4.7] -> Save the Entries.

Release version :
4.7 : 620 , 4.6B : 46B , 4.6C : 46C , 3.0A : 30A , 3.0G : 30G

SEND ( ALE )

19th MARCH

PORT Number :
IS THE SERVICE ID for the Application Running in the Operating System as
servers.

Example :
If oracle server is installed in any Network , the services of oracle can be identified
using Port Number "1521". Client network with help of Host String

scott/tiger@oracle
@oracle : is called as Host String specifies the network id for Oracle Server in the for
the TNS network listener for Oracle Connectivity.

Java Web Server:

is identified with a port number called as 8080

Weblogic Server :
is identified with port number called as 7001
http://project-2:7001/examplesWebApp/index.jsp
EDI ( Electronic Data Interchange)
Is a Sub system in the SAP application server to provide data transactions between
different SAP servers , SAP to Internet Server Communications or SAP to Non SAP
communications.

EDI sub system is a collection of IDOC ports as

1) TRFC ( Transactional RFC ) : is a services in EDI sub system to take the request from
the current system to process into remote System with help of Logical System. This
service can be used to take request in the form of Function Module.
Note : It can Get the data from remote System into current system but can't Send the data
from Current System to Remote.

2) File Port :
Is the Most Important Port for ALE trasaction controls with two Sub Services as
OutBound Process and Inbound Process.

OutBound Process : is a service to take the request from the current System into IDOC
to deliver the data into remote System with Help of Function Modules.

InBound Process : is a service to take request from remote System into current system
with help of IDOC's and send the data collected into current system using Function
Modules.

3) CPI-C : Common Programming Interface - ( communications)

Is a service can understand the a type of language called as CORBA ( Common

Object Request Broker Architecture ) using IDL ( Interface Definition Language ).
This port can be used for NON SAP application to pass a request like Siebel , java
or VB to be interacted with SAP.

4) ABAP-PI ( ABAP programming Interface )

Is the service uses ABAP created Drivers to communicate with Remote System,
Is the BASIC concepts of BAPI applications.
When ever Non SAP sends the Request in the form Of BAPI request is collected
by these services and request is processed using "TRFC" PORT.

5) XML - HTTP
This port in EDI sub sytem is used for Web Transaction for the type of Application ITS,
WAS or Netweaver.
XML is used in SAP to provide data security and web request is processed using
"HTTP" protocol. These transactions are called as logical transactions.

6) XML-FILE
This port used for Web technology communications to transfer Physical data
communicates between the servers.
21st MARCH(Partner Profiles)

EDI :

TRFC ( RFC )
FILE ( ALE )

ABAP-PI
CPI-C USED FOR NON SAP COMMUNICATIONS

XML-HTTP
XML-FILE INTERNET BASED APPLICATIONS

IDOC PORTS

ZIDOC930
CREMAS : Existing IDOC in SAP for Transfering Vendor Data to the Remote
System

MATAMS : Is the Existing IDOC for Material to be transported from One System to
Remote System.

DEBMAS : is the IDOC used to Transfer Customer Data from current R/3 to Remote
R/3.

If the IDOC are existing in Data base Layer, how to add these into Application Server
EDI Sub System...?

PARTNER PROFILE is a concept used in SAP to Attach IDOC into SAP Application
Server for the type of Partner.

Partners can be classfied as

Ilogic : Customers ( Students )

Ilogic : Material Suppliers ( Vendors )
Ilogic : Bank Transactions

Logical Systems : is a Network Indentifies the Remote Networks.

This Logical System is in SAP at Application Server level, to Control the data to be
transfered from current System to remote System or Remote System Data to the current
System.
 Partner Systems is the Concept used In EDI for Attaching IDOC into EDI Sub System
using the type of Partner as.

1) Partner Profiles for Vendor:

Vendor is a person or a company used to supply th material, can be created
from a tcode as "MK01".
If the Vendor is created from MK01 can be used to transport the data of the
current R/3 into remote R/3.
To do this with help vendor name we can generate One Partner Profile using
"WE20" TCODE.

But Using This partner Profile We need to depend on Vendor Master Data every
Time.

Transfering the data based on Customer, Vendor or Bank is not Suggested.

SAP Says if the R/3 to R/3 communications Use the partner profiles for the type
"logical System".

Note: OutBound for the Logical Systems are Auto Generated in SAP while transfering
ALE, as ABAPer We need not do any configurations for Outbound.
But we need to Configure InBound process to collect the data from Remote R/3 System
into Current R/3 System.

To Do this Use following Navigations.

1
Main Theme of the Partner Profiles is as Follows then we go for Navigations.

Transfering data from SAP3 into SAPABAP.

1) MATERIAL IS CREATED IN SAP3 AS "NCNYSR01".

Transfer this material to Remote System SAPABAP.

2) From SAP3 need to Send the material to remote SAPABAP.

to do this

Create Two Logical Systems

1) NCNLS
811 : SAP3

2) YSRLS
800 : SAPABAP.

SAP3 HAS A PROBLEM Is unable to create TRFC port, so Conver the data
Transactions from SAPABAP to SAP3.
22nd MARCH Navigations for Partner profiles and ALE

Navigations to Configure Partner Profiles with Inbound Process in the receiving System.

1) Create the Logical System

i) Define Logical System

ii) Assign Client To Logical System
iii) Assign Network To the Logical System.

This logical System name should be same name as Logical System Defined in Sending
System.

2) Generate partner Profiles.

WE20 -> SELECT PARTNER TYPE LS (LOGICAL SYSTEM ) -> CLICK ON NEW
FROM APPLICATION TOOLBAR -> SPECIFY FOLLOWING

PARTNER NUMBER : SENDLS

(NAME OF LOGICAL SYSTEM)
PARTNER TYPE : LS
Type : O ( organizational unit )
Agent : 50010120 ( EDI / ALE department )
Language : EN

-> Save the Entries -> Object is created in the Data base and Configured in Application
Server EDI sub system.

-> Click on Create Inbound parameters from the application screen ( + pushbutton on
screen ) -> opens an interface -> Specify the message type ( CREMAS ) [ for vendor
records]
/ matmas (for Material data ) / DEBMAS ( for Customer data ) -> Specify the Process
code ( CRE1 process code for vendor to execute the function module to insert the data
into current data base ) -> save the entries -> come back.

Configuring Outbound process In Sending System to process Record data to be

transported into Remote Systems.

1) CREATE two logical systems, to represent one logical system for sending , another
logical system as receiving.
i) SENDLS
ii) Recls
2) Assign Logical System to the Clients.
i) SENDLS : 800
ii) RECLS : 811
3) Assign Networks to the Logical System
i) SENDLS : SAPABAP
ii) RECLS : SAP3.

4) Create Model Views

Model view is an object in SAP assigned with Sending and Receiving Logical
System and Also with a Logical Message of the IDOC. This is used in SAP to generate
Partner profiles for OutBound process With Help ALE Navigations.

Use Following Steps to Configure Parner Profiles using Model Views.

i) Create Model views

SALE -> ALE -> Modelling and Implementing Business Process -> Maintain
Distribution Model views -> opens an interface -> Change the mode of the screen ->
Click on Create Model views -> opens another interface -> Specify the short text ->
Name the Model view in Technical Name ( 930mv1) -> staring data of mvew creation
and ending date -> continue .
Model view is created.

ii) Assign IDOC and Logical System to the Model view .

Select the Model view created -> click on Add Messages from Application Toolbar ->
specify the following

SENDER : [ sendls ] ( sending Logical System )

RECEIVER : [ recls ] receiving Logical System
Message type: [ CREMAS ]

Click on Continue -> Save the Entries.

iii) Add the model view in Transportation System.

Select the model view -> click on edit menu -> model view -> transport -> assign with a
request number.

iv) Generate Partner Profiles

select the model view -> click on Environment menu -> generate partner profiles ->
opens another interface -> name the receiving logical system [ recls ] -> execute -> SAP
generate a message as

i) Partner profiles is created

ii) TRFC port is created.
iii) OUTBOUND process is Configured Success fully
v) Distribute the model views.

select the model view -> edit menu -> model view -> Distribute.

Using This step Physically Object are trasported to the APPlication Server and ready
for Data Distribution.

Example navigation to transfer The record Data from One Client to Another Client Of
the SAME r/3.

WE CREATED A VENDOR AS 1900 IN SAPCLASS

( 800 ) CLIENT , SEND THIS DAT ATO REMOTE CLIENT AS 811 AND VERIFY
THE DATA.

1) CREATE TWO LOGICAL SYSTEMS

PRAVEEN ( SENDING LOGICAL SYSTEM )
CREDDY ( RECEIVING LOGICAL SYSTEM)

2) ASSIGN CLIENT TO LOGICAL SYSTEM.

OPEN 800 CLIENT PROPERTIES -> ASSIGN PRAVEEN LOGICAL SYSTEM TO

800 -> SAVE THE ENTRIES.
OPEN 811 CLIENT PROPERTIES -> ASSIGN CREDDY LOGICAL SYSTEM TO811.

3) ASSIGN NETWORKS TO LOGICAL SYSTEM.

for Praveen ( Logical System )
CLIENT : 800
LANGUAGE : EN
USER NAME : SAPUSER
PASSWORD : ILOGIC
TARGET HOST : SAPCLASS.
for CREDDY ( Logical System )
CLIENT : 811
LANGUAGE : EN
USER NAME : SAPUSER
PASSWORD : ILOGIC
TARGET HOST : SAPCLASS.

4) Create Model views

i) 930MV2
ii) Assign Logical Message for Model view .
MODELVIEW : 930MV2
SENDER : PRAVEEN
RECEIVER : CREDDY
MESSAGE TYPE : CREMAS ( FOR VENDOR )
 -> CONTINUE -> SAVE THE ENTRIES.

iii) add Modelview in Transportation System.

select -> edit -> model view -> transport .
iv) Generate Partner Profiles
select -> Environment -> generate partner profile -> enter Receiving System name
( CREDDY ) -> execute .
v) Distribute the model views.
______________________________________
Sending System Configuration are completed.
______________________________________

In the Receiving System ( 811) configure Inbound process.

( we20 -> partner profile for logical system [ praveen ] -> assign with cremas ( cre1)).

As Vendor is not created in 800 client to be transported, we created a vendor as "1900"

To Transfer the Data of vendor we can use

BD14 : FOR VENDORS

BD12 : CUSTOMERS
BD10 : MATERIAL DATA ETC.

ALL "BD" tcode are used to transfer the data from Current System ro the Remote
System with helo of Logical Systems and IDOCs.

So Use BD14 to transfer Vendor from 800 to 811.

BD14 -> EXECUTE -> 1900( VENDOR NUMBER ) -> MESSAGE TYPE ( CREMAS )
-> TARGET SYSTEM
( CREDDY ) -> EXECUTE -> SENDS THE RECORD INFORMATION TO THE IDOC
EXISTING IN EDI SUB SYSTEM -> AND TRANSPORT THE IDOC TO REMOTE
SYSTEM.

To check the status use -> WE05

WE05 -> EXECUTE -> DISPLAYS THE IDOC STATUS.

Transfer A customer from Current R/3 to Remote R/3.

To define Customer use "XD01" Tcode.

DEBMAS (IDOC)
BD12 Tcode to Send Customer Data
( DEBM ) Is the process Code.
IDOC STRUCTURE