Emax Volume 4

INDEX
SNO Chapter Pages

1 Introduction 02
2 IDocs & Message Type .,:(I1 .+
-'**-
3 communication Settings~ - 12
4;.4$$?6',, zqw22
s,p,, .- ,%-
4 Outbound & Inbound @Y2- .+F22 ,

4
5 Distribute Master 9Byfg2yia @

?%CZr\ r : . %
Sp,%
2"
a
a
+!:.*:"
:
-is
>
Standard IDoc %, *4&$ j

,-c
-5-
?% "Tv
f ..." ,
6 Filtering . L- ~ ~ 21 ~ , L u--
zz%%
,* .a -,r e> - -
i
r *il
7 Trouble Shooting & 07

Recovery
8 Custom IDocs 30
1 . ~ I T ~ ~ D R I SXEROX
,.A ..A . . - - C
, ES
Floc No: 40, Gayatlui Nagar, Behind HUDA,
SOFTWARE INSTITUES MATERIAL AVAILABLE
Arneerpet, Hyd. Cell: 98666 84838
1. Introduction to ALE
We Never Compromise In Quality. Would You?
ALE (Application Linking and Enabling)
ALE is SAP'S technology to support distributed yet integrated processes across several
SAP systems.
(OR)
Application Link Enabling (ALE) is a set of business processes and tools that allow
applications on different computer systems to be linked. This can be done between
different SAP systems as well as between SAP and non-SAP systems.
Distributed Process:
A distributed process is one in which part of a business process(Sa1es) is carried out on

one system and part(Finance) on another. The two systems
each other at appropriate points to stay synchsonized.
Need for Distributed Process:
Business in D
No11 availability of dedicated net
Cultural and 1
Maintenance downtime etc.).
. It was inlpoi-tan: from

data on businlss rules, not on database
ng integrated as one
endently and support
Distributed systems that can handle different data models. A local implementation
should be able to customize the system to meet its local needs.
Receiving systems that can handle their own problems and not tie up the sending
system.
Systems that maintain continued operation in spite of network failure. Changes made to
either system should be syncl~ronizedafter the network connection is restored.
A sound technology and methodology that can be used in all distribution scenarios.
SAP Distributed environment:

ALE allows for efficient and reliable communication between distributed processes
across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A
message defines data that is exchanged between two processes. IDocs are containers that
hold data exchanged between the two systems.
Page 1 of 2 By Ganapati Adimulam
eMax Technologies,Ameerpet,Hyderabad
Ph No :+91 40 -65976727, Cell NO : 99484 44808,98490 34399, w\~~v.emaxtech.com
1. Introduction to ALE
Benefits of ALE
- - -- -- - . -- - --- --
Integration with non-SAP systems: ALE architecture allows third party

applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message
is determined, ALE delivers the message to the recipient. If there is any network
problem it will buffer the message and delivers the message once the network is
restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new
release of SAP without affecting the functionality.
backward compatibility of messages
ALE may also reduce costs, in particular costs of

is run on one integrated system you have to upgrade the who1
entire company is affected

for the new release. Within
interfaces, like those provi
not involved and need no tra
known to all ass you to immediately trigger an IDoc sent to

all associates as soon er record is created in one system.
Another common scenario is that a company uses different installations for
company accounting and production and sales. In that case, ALE allows you to
copy the invoices created in SD immediately to the accounting installation.

eMax Technologies,Anieerpet,Hyderabad
Pi1 No :+91 40 -65976727, Cell No : 99484 44808,98490 34399, w~nv.emaxtech.com
2. IDocs & Message Type in Detail
IDocs
Note : ALE Uses IDoc(1ntermediate Document) to carry the Data across the Distributed
Systems.
Note : IDoc is SAP'S Own Foimat so that only SAP Systems Can Understand the data in
IDoc Format.
Scenariol: SAP - SAP
Note : Since Both the systems are SAP Systems, they ca

IDoc Format.
Scenario2: SAY <-> Non -SAP
/*
EAI(Enterprise Application Jiitegration) Tools
When the Communication is bet SAP <-> Non SAP , The data in IDoc Format
should be Converted in other f o r r & t ( ~here)
~ ~ and the Any other format should be
converted into IDoc , We Can go for any EAI Tool which can do the above Conversion
With no Loss Of Data.
Note : IDoc is Collection of Segments AND Each segment is collection Of Fields.

Note :SAP ALE Consultant role is always to Work with IDocs irrespective of the Other
System(SAP/Non-SAP).

eMax Technologies, Ameerpet, Hyderabad
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emaxtcch.com
/DOC Design Guide Lines(Syntax Rules)
IDOC Type defines the structure and format of the business document that is to be
exchanged.
Analyze the Application Data to be transferred Via IDoc AND
Identify the List Of required Segments
Make Sure that the related data is grouped into one segment
Decide the Parent & Child Segments
Decide the Minimum & Maximum No Of Repetitions of each Segment
Decide the mandatoryloptional segments
Make Sure that the Segment length is not more than 1000 bytes(Char).
Segments
Seginen.ts are reusable

components.
- Segment Definition (versiou dependent)

\ %
v * * ,d"
- Segment Documentation yb&-*,F
*;'
The last 3 characters is the versioil of the segment
Definitions keep changing as per the version but the segment type remains the same
Note: Fields in any seginent can contain only alphanumeric values(Data Types).
Data Types Description

CHAR Character String
CLNT Client
CUKY Currency Key, refrenced by CURR
fields
DATS Date Field ( YYYYMMDD) stored as
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emastech.com
Note : All the Standard Segment names starts with E l and So that it is
recommended to start the Custom Segments with 21.
/DOC Run-Time Components
An IDOC is an instance of an IDOC Type

%
At run time the following events occur
One control record is attached to the IDOC
Segments are translate into data records

'".
Status records are attached
A unique IDOC no. is allocated by
I Control Record 1 I Data Records 1 I Status Records I

I I I I
1
A) Sendor & A)Application A) Status of
Receiver Info Data IDOc Journey
B) Only One B) <N> No Of B) <N=-No Of
Record Records Records
C) Table is C) Table is C) Table is
EDIDC EDIDD EDIDS
IDOC Number Links

all types of Records

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, ~v~vw.ernaxtech.com
IDoc Creation :
IDoc is Collection of Segments
Each segment is collection Of Fields.
Ex : IDoc : DEBMASOl (Customer Master) - Standard IDoc.
I
5
Se ment Name
ElKNAlM , KUNNR, Customer General Data
1 ElKNBl 1 KUNNR, BUKRS,ZTERM,. .. Customer Company 1

1-
I
i
- -1 Code Details 1
ElKNBK KUNNR,BANKS,BANKL,.. Customer Bank Details
( Etc.. .
Note :All the Standard Segments starts with E l it is recommended to start
the Custom Segment names with Z1.
IDoc Creation Is a TWO Step Procedure.
1) Create the required Segments through Seg
2) Create the IQoc ( Arrange the already Created Segments in the required
Order) though IDoc Editor(WE30).
Stel, 1 (Segment Creation ) in Detail :
Execute WE31 and

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, ~~ww.cmaxtech.com
j Segrnentfiipe attribl~tes
+----..- - ,' I II I I
8
; Segment ffpe Z I Kf4AI r?
- Qualified segment
j -------,
:I
:Short Descriptiuni
:----_r-----------.------
Custorner General Data
SAVE it and BACK.
Edit -> Set release.

Ph No :+91 40 -65976727, Cell No :99484 44808,98490 34399, www.emastech.com
Note : Releasing the Segment indicates that the Segment Development is Complete
so that further Changes are not allowed and also to make it available in IDoc
Creation.
2"dSegment : Customer Company Code Information

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~vw.emastech.com
SAVE ,BACK and Edit -> Set Release.

Note : Standard Segment names starts with E l so that it is recommended to start
the Custom Segment with 21.
Step 2 (IDoc Creation ) in Detail :

Execute WE30 (IDoc Editor)
i N e w- b- a s i c l D u c t5ampe,.-*'
-
/ .p- Create n e w
" -"
iCreate a s coPj2 c o p y from

I I
I ,
--&.
4
F------
I .
----
Create s u c c e s s o r
-" -
- "-
Adrr-iinistrat~on
- -- - --- ,'r '
-- -----
-A*--A-
-"
" L--.. --->-

Successor of
-- ----' "
-- --- "4- A"
- "---
------ "b
"
- ..- "-. 2 /
"&.
Person responsible SAPUSER

/I Processing person SAP U S ER
--
-**--
Description
V "
- ---------.
" --- - 2 >
>-""- -*"-."- -
"-.
---
*-a
-
$1 s
-- -- ""
,
,/"
I lDoc For C u s t o m e r Master

Ph No :+91 40 -65976727, Cell No : 99484 44808,98490 34399, www.emaxtcch.com
Select Create new and Provide the Description then Continue (ENTER).
[B-
pJ,?&
-2
@ ~ 2 Pz" <Q
( c r e a t e s e g m e n t ... hiit it+^^)(

- p~
IOoc F o r C u s t o m e r M a s t e r
Select the IDoc Name and Say Create (Insert) Segment --.--).
TO ADD NEXT SEGMENT

Select the Segment after
..-
which you want to ADD the new Segment and Create
j[Zl/
(Insert) Segment '.-,--..J.

eMax Technologies, Arneerpet, Hyderabad
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emastech.com
We Never Compron~iseIn Quality. Would You?
ENTER.
" - e 9 of 11 By Ganapaii Adimulam

eNIax Technologies, Ameerpet, Hyderabad
Ph No :+9140 -65976727, Cell No : 99484 44508,98490 34399, w~~v.cmasiecl~.eom
We Never Coluprolllise 111 Qi~ality.Would You?
ancel ele ease.:.

-
Object directory entry .. t,. ..:. ..,
Congratulations ! . IDoc ZDEBMASOl(Customer Master ) is Created

Successfully with TWO Segements : ZlKNAl and ZlKNBl.
Message Type :Message Type is the Unique Identification of the Application Data
which-is been transferred through the IDoc.
Note : The Same IDoc Can be used to transfer lllore than one type of Application Data
So that IDoc name is not enough to Identify the Application Data Currelltly being

eMax Technologies, kmeerpet, Hydel-abad
Pli No :-1-91 40 -65976727, Cell No : 99484 44808,98490 34399, ww~v.emartech.co~
We Never Cornpromise In Quality. Would You?
transferred to IDoc. So that we need something to Identify the Same, that Some thing is
this Message Type.
IDoc ZBLOANS For Bank Loans
segment Description
I ZI EL Entertainment Loan 1
Z 1HL Home Loans

ZlPL Personal Loans I
We Cannot provide the List Of Segmenfs to be

ram For Generating the /Doc for Message type
the Data only for the respective Segments-
n Segments. Similarly at the receiving System.
1 Message Type
- p~
IDoc
ALEREOOl 1 MATFET (Fetch Material)
ALEREQOl DEBFET (Fetch Customer)
ALEREOOl CREFET (Fetch Vendor)
Note : The Same IDoc ALEREQOl is ised to fetch any Master Data and Fetching
Each Master Data through a Different Message Type.

Ph No :+91 40 -65976727, Cell No : 99484 44808,98490 34399, n~v~s.emartech.comm
3. ALE Communication Settings
ALE Communication Settings :
Note : Con~municationSettings acts as bridge between the Participated
Systems and so these are one time settings.
Note : Sending Data To and From SAP System is always via Client So that the
Participating Client should be Identified Uniquely.
SENDOR RECIEVER
Clients : Clients :
100
110
Requirement: Maintain the Communication Settings Between

SENDOR System (800 Client) and RECEIVER System(810 Client)
Of the same SAP Server.
I I
1) Identify the Participated

Names(Logica1 Systems)
to the Participated Clients.
Client - 810

ENTER
?
Note : Notice the Caution - The Table is Cross - Client.

i.e The Same Data is Created in all the Clients of the Same SAP
Server Automatically .
New Entries
" "
ystem through New Entries for Receiver Client 810 and

eMax Technologies, Ameerpet, IIyderabad
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~)v.emaxtec~.com
Note : Here We Work with Two Clients (800

Server so that the Logical Systems are crea
the Clients, Else the same should be C
B) BACK to the Initial Screen of.SALE

.. ~
,*,*.,@$&,
..
, ~ \ \.!<\
.;,.2$$\r:<
Sending & Receiving Systems$@~i$:~

...\? .:*
.) Logical Systemsv->
s*.~?,Assign
,.: C \ .<:+\~
\, \\,\ \.. \,
I \.' \,
I . . . . , . ., . . . . . . ... .
'@A,~.ss~gnClrent to Logical System

Convert Loaical Svstem Names in Asslication Tables

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w\nv.emaxtec&.com
Select the Participated Client (800) and Details
SAVE it.
Note : Repeat the Same in the RECEIVER System i.e to Link the Client 810 to the
Logical System RECEIVER. 4

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, wwv.emaxtech.com
We Never Compromise In Oualitv. Would You?
LOGON to 810 Client (RECEIVER)
Execute Transaction SALE .
Sending & Receiving Logical Systems -> -+y$%

.) Logical Systems -> Assign Clie~'t~to&ogical
Syst
Ckaage View rrC##&nb ": Owem8w
Enter the Logical System RECEIVER and SAVE it.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~w.ei~~axtecl~.com
3. ALE Communication Settings 4
Note :Now the Participated Clients 800 as named as SENDOR and

810 as RECEIVER.
SENDOR Logon Details RECIEVER

Client : + Client :
800 4 810
Lopon Details
.5!
Note : in the RF'C Destination, We Provide the receive^-8s Details(1P
Address) and the Logon Details of the Receiver
LOGON to SENDOR Client(800)
EXECUTE SM59.
4
Select

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, \nnv.emaxtech.com
3. ALE Communication Settings 4

Ph No :+9140 -65976727, Cell No :99484 44808,98490 34399, ~7~1v.eniaxtecli.com
We Never @ompromiseIn Quality. Would You?
WFC D-fC!tatC@n RECEIVER
Provide the HostName (SAY Application Server Name) and System

Number of the Receiver SAP System.
I I
to provide the Logon Details of the

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~vw.emaxtech.corn
We Never Compromise In Quality. Would Yo1
Provide : Client of the RECEIVE
TESTING the RF'C ~ e l t i ~ a t i o: n
j Remote ogon \1
Click On Remote Logon *-"------"
- - - from the Same Screen.
eMax Technologies, ~ k e e r ~ eHyderabad
t,
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~wv.emaxtecb.com
And Make sure that you are able to LOGON to the RECEIVER System(C1ient).
I F U connections
~ I
I l n t e connections
I Logical destinations I
1 T C P - I P connections I
I Connections via ABAP14 d r i v e r I
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~wv.e~naxtecl~.com
. W2 connections (Type 2) - Type 2 entries specify W2 systems.
R/3 connections (Type 3) - Type 3 entries specify W3 systems
TCPIIB Connections (Type T)
Type T destinations are connections to external programs that use the RFC API to
receive RFCs.
Destination Parameters
Technical settings
entry help according to the above types discussed.
Trace :Mark the Trace option to have the
using report RSRFCTRC.
Loud balance :If you choo

information:
.on to the target system and

n z Monitor -> Servers.)
art Of Communication Settings)

dium of transferring Data.
Port ( Transactional RFC).
-
LOGON to SENDOR : EXECUTE WE21

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w ~ v . e m a x t e c l ~ . c o m
Select Transactional RFC ( mi~!ansactional RFC! ) and Create.
.~$>
,
,, ,.\. '...,,:
~\
Continue with Generate Port name
n (Logical System Name) of the

Receiver's Cli
h was Already Created in the Previous Step.
tion, When the Communication is a TWO Way

4
Note : All the Communication Settings are Completed .i.e the Bridge
is Ready so that the data can be transferred via IDocs between
SENDOR(800) and RECEIVER(810).
Note :Since all these Settings involves System Details , BASIS

Consultants will take care of Building the Bridge (Communication
Settings) in Realtime and also it is one time job between each sendor
and Receiver.

eMax Technologies, Ameerpet, Hyderabnd
Ph No :+91 40 -65976727, Cell No : 99484 44808,98490 34399, w ~ ~ v . e ~ ~ i a x t e c l i . c o ~ ~ ~
4
4. Outbound & Inbound Process
We Never Colnproinise In Quality. Would You?
ssoutbound (IDoc Generation & Dispatch Process) in Detail
Data Records For all the
Physical Sequence Of
................................
Sendor Receiver IDoc
Receiver MODE
Outbound Pro
ed for Sending the IDoc : Whenever the Master Data is Created
t Consults the ALE Layer to deterinine whether any system is
data. If So, ALE Layer starts the Process to send Material Master
Master IDoc : The Docuinent / Master Data to be sent is read

atted into an IDoc Forinat. This IDoc is Called
Master IDoc. 4
3) Generate the Communication IDoc : ALE Service Layer generates a Separate
1Doc from the Master TDoc for each recipient who is interested in the Data.These
recipient - specific IDocs are called Coin~nunicationIDocs and Stored in the
Database.
Note : The Recipients are determined froin the Distributioil Model that Maintains
the list of Messages(1Docs) exchanged between two Systems and their direction
Flow.
4) Deliver the Communication D o c : This Step Delivers the IDocs to the
appropriate recipieilts using the Asynchronous Communication Method
and using the details fro111the Outbound Partner Profile. Asynchronous
eMax Tecl~nologies,Ameerpet,Hyderabad
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, ww~~~.emaxtech.com
4
4. Outbound & Inbound Process
We Never Colllprolnise In Quality. Would You?
Communication Method allows the Sending System to Continue its Processing

without having to wait for the destination system to receive / Process the IDoc.
Inbound (IDoc Receiving & Posting ) Process in Detail :
Inbound
Program
Read the Data from the Communication IDoc
Database Post the Data in the respective
ALE Inbound Partner Profile
IDoc Inbound Progl

Process Code
------- ------------------
DEBMAS DEBM
CREMAS CREMlCNl
MATMAS MATM
I Communication Layer
I
Inbound Process :
*-J
Note : The Inbound Process receives the IDoc and Creates the Applicatioil
Document(Data) in the Receiver System.
1. Store the IDoc in Database : IDoc is received in the System and stored in the
Database.
2. Invoke the Posting Program/Function Module : Posting Program is identified
from the Inbound Partner Profile and the IDoc is then transferred to the
Posting Program.
3. Create the Application Document@ata) : The Posting Program reads the data
from the Segments of the IDoc and Creates the Application Document in the
Systein(Updates the respective Database Tables).

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~~w.emaxtech.com
5. Distributing the Master Data Via Standard IDocs
We Never Colnprolnise In Quality. Would You?
Distributing Master Data

Types Of Distributing Master Data:
1) Send / Push Whole Copy.
SENDOR RECEIVER
Get/Fetch/Pull Whole Copy
Send Changes Only (Cha
,B
%
, %-
--/
Send I Push whol?coRy/in Detail.
SENDER RECEIVER
Note : IDocs ,Message Types ,Outbound and Inbound Programs are already
provided by SAP. So that When We use standard IDos to transfer Data, I t is
enough to Configure both Sender and Receiver Systems Because everything is
already Provided by SAP.
I Requirement: Transfer the Cost Center Master Data and Post(Create)

the Same in the RECEIVER(810).

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~w.emaxtech.com
4
Steps to Transfer the Data through Standard lDoc :

$
Maintain Outbound Configurations For COSMAS:
Make Sure that all the Communication Settings are in Place. (Already
Completed & Tested).
J2 Maintain the Distribution Model ( BD64 )
3J Maintain Outbound Partner Profile ( WE20 )
A) Maintain Distribution Model in Detail: Create the Distribution Model and Add
the Message type to be transferred.
Z,$%?i
EXECUTE BD64 AND Click On Change 14
1
2
. -
1 ; a!F p:.
-,------w?-?v
s!d+i~,p.~~
~is~!..v'anqectmoa-.-
rlllerrnodrl .display.
..
. <: : :
/Descr=nnical
. ...iV?-.!I
-~-~-m.,.-__-.-,--"
.............
name
. :,.!:! r>:S: :. . ',,.,,..
x.,
.. ,.
--,----
~ u s l n e s sowect
-.-,-.. . . . . .
-.
""*
2n Model vlews
: 0 % ,;:. ,AL . N o Short f e n exlsts
( p % .*.;. .:< BBP-011 NO short text ~ X O S I S
BCS9 ~ - 8 0 0 . NO shortfextenists
RELCO . N o snon l e d exists 4 bc
I rz A
- i: . < ;I,,.,.. 81T300LBP N O shortled ex1SlS
i % ::..;:::':.i:,:a
a :>I .:;
:CONSOLIDAT. N O short lent eesls
DlLID3 NO snort ted exists
! b
L> .. t -' .:; .: : D<Z_IOPCLN. N o shortlext eilsls
iEBP3OO-R3. NO shorttext exlsls
HR-ORG-SEM N o shorltextexisls
LIS NO 5 h o r t l e x I e a ~ l s
.... iOSB-SUPPLY. N O shod l e d exlsls

PFS N o snort text eiAsls
2 b % .:::.. ,!.: , s. : ! :",,': :SUBSYSTEMS. N O short l e d exlsls
i uz ;..?... WlvlS N O shorttext e ~ i s l s
! OX.,. XI .
r10 short l e d exists
1 ,::<
, iZ8" N O S l l O l l t e k f exist*
1 % ::.;,( ,
. : <>. :r>y , ! . .
1 , x i....., ::; :, , ;.....
: :,:
iE2W-lDES
'DE3-WBi\
i
1 L> :..&. .
..i... ::.-
,.,,<
.
:;,, . ..,...:;.
t, :;,..,::,: ,;..,;
iDU3.bID3
EBPIO-R3

eMax Technologies,Ameerpet,Hyderabad 1
Ph No :+9140 -65976727, Cell NO : 99484 44808,98490 34399, www.ernaxtech.com

NO shod tea exists
XI NO shorl
.ZBV Nosh0
SAVE it.
new Distribution Model for each receiver and Message Type.
Note,: Distribution Model Acts as a BAG to Carry the List Of Receiver Details for
any Message Type and Any Receiver from the SENDOR.

We Never Co~npromiseIn Quality. Would You?
For Each Message type to be Transferred :
Select the Distribution Model andclick On Add Message Type 1--Add message type j a
AL . N O Shorttext exists
BBP-Dl1 N O ~ n o r t t e x exist5
t
BC619-800. No shorttexi exists
BELCO . N o shortleldex~sts
BlT300-BP No short texi exists
CONSOLIDAT. No short teM exists
DIZ-ID3 . NO shorttext exists
DIZ-ID3CLN. No shortteMexists
EBP300-R3. N O shorttext exrsts
HR-ORG-SEM. NOshort leMewsts
1 b <:.; LIS N o shorl lexi ~ X \ S ~ S
LO21 5 . NO shorttext exists
'IUIARCUS . N O ShorttexieXiSts
OSB-BUYER . N o ~ h o r t t e x i e x l s l s
OSB-SUPPLY. Na snorttext exists
PFS . N o shotltexi exlsts
SUBSYSTEMS. N o short tern ~ r i s l s
WlvlS .Noshort l e d exists
XI . N O short lexi 8x1~15
ZBV NO Shontexi exists
BZB-IDES
DE3.KABA
DH3->ID3
Y ?- 5 O Ad0 BAPI
,.--.---- ~
ooctnbuslen ~ a m ,
FFllter momel Olsnlsy
,
Creele r n O G s l u l e w
"AL-
~ e : c t ~ p t i o n , t e e n n ~ c i "rme
.~
Add mes4s.e
--
hpa
B"e,n..I OblSSl
__-___--- --
- A
-? Moue8 "lBWS
AL N O short Lad e x , s , s
BBP-DII N O Snortten exllls
'a0019_800 N 0 5non,en ex1515
SAVE it.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~w.emaxtech.coni
We Never Comprolnise 111 Quality. Would You?
B V Filter model display O create modelvlew O~ d BWI

d add messagevpe
A : -
-
2 - . . : : - d 2 - - - - - ."
--- ..-2r
1Dlstrlbutlon Model D e s c r ~ ~ I ~ o n I t e c h name
rl~~al Business oblect
C619-800 No short text exists

ELCO .No shorttexiexists
iT300-6P. No shorttext exists
ONSOLIDAT. No shorttext exists
1Z-ID3 . N o shotttedexlsts
DIZ-ID3CLN. No snorr lext exlsts
E B P 3 0 0 - R 3 NOshort text exists
:HR-ORG-SEM. No shod lext exists
LlS . NOsliolttexiexists
LO215 .NO shorttexiexosts
'MARCUS No shorttext exists
OSB-BUYER . No shorttexi exists
OS8-SUPPLY. No sliorttent eHsts
PFS . No short text exist
WIS . No s!lOrilexie
W "
XI . No shorttekieHs
:/ p g zz:: ZBV . No short lext exis
'i D g O1; 2 IDES ;.EL.
r y ~ ~,,s~;~,;~;~:,;,:;p~<;,
.
828-IDES
i DE3-K48A
Notice t h a t , the Sendor, Receiver
DH~- ID^
and Message Type Details Are
i> gr<,:aac~,~?.,:j
..-.
< ~...~. .
..-..-.. ---. - c:];~:,!
...~..;..,.~.-;..~...
: .C I.-
; :..
~-.
~.~-- .-..-.......:.
EBP-TO-R3
--............-..--. ... ADDed -
.I " %.r~~?!!@
~!~~."!.C:!.P~!~?"!I~!~??.~....~.~~.IE;!E!~.~!L~
e00~1inei SENDOR
8 + 810 disent RECEIVER
,
Note : Repeat the ADD Message type Steps for each message type to be
Transferred.
B) Maiutain Outbound Partner Profile(WE20) :
Note: In the Outbound Partner Profile ,We Maintain the Below Information.
Medium Of Data Mode Of Dispatch
.Immediate/
Note : We always Create Only One Profile for each receiving(Partner) and One
Entry for each Message type we transfer.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, ~~~w.emaxtech.com
Note : A Profile is Created For RECEIVER (810 Client) So that we have to use the
Same Profile, every time we transfer a new Message type to this Reciever.
For Each New Message to be Transferred to the Same Partner (RECEIVER):
From the Same Screen - WE20

Select the Partner and Click Create Outbound Parameters

eMax Technologies,Ameerpet,IIyderabad
PI1 No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emaxtech.com
ENTER
1 = WHOM TO SEND (RECEIVER)
2 = WHAT TO SEND (MESSAGE TYPE IDoc) +
3 = MEDIUM OF DATA TRANSFER (PORT)
4 = MODE OF DATA TRANSFER(IMMEDIATEIC0LLECT) 4
SAVE it.
NOTE :ALL THE OUTBOUND CONFIGURATION SETTINGS

ARE COMPLETED. We Can Transfer the IDOc But it Fails in
Posting the IDoc in the INBOUND (RECEIVER) Sys. So Before We
Transfer the Cost Center Master Data ,it is better to Complete the
INBOUND Settings also to TEST the Complete Cycle.
'I'
INBOUND Configuration Settinpts: " <
MAINTAIN INBOUBD Partner profile (WE20) :

We Never Co~npromiseIn Quality. Would You?
SAVE IT.
SELECT THE Partner SENDOR AND CLI BOUND

PARAMETERS ID. /
Page 9 of 39 By Ganapati Adimplam

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~+w.emaxtech.com
We Never Colnpromise 111 Quality. Would You?
NOTE :BOTH OUTBOUND AND INBOUND CONFIGURATION

SETTINGSARE COMPLETED. WE CAN TEST THE COMPLETE
PROCESS OF SENDING THE COST CENTER AND RECEIVE IT
AND POST(CREAT) THE SAME IN THE RECEIVER SYSTEM.

We Never Coinprornise In Quality. Would You?
TESTING THE PROCESS :
1. EITHER CREATE A NEW COST CENTER (KSO1) 1 SELECT THE

EXISTING COST CENTER FOR BD16.
EXECUTE BD16(SEND COST CENTER) AT SENDOR SYSTEM

Send G W ~center
'1 Sewer group

Cost tinters per process 20
4
Enter the Controlling Area 1000(Standard) ,Cost Center - 3500 ,Message type -
-' 4-&
COSMAS and Target System as RECEIVER and
EXECUTE IT
ENTER

cMax Technologies,Ameerpet,Hyderabad
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emaxtech.com
We Never Co~nproiniseIn Quality. Would You?
ENTER.
4
EXECUTE WE02 / WE05 TO CHECK THE IDOC NO AND DATA RECORDS
AND STATUS OF IDOC.
00.00 DOE, lo 24:OO.OO 4;

-
0 6 02 2008 LO 06 02 2008 e;
-,
0 0 . 0 0 00 10 24.00-00
4
te o f ~ a sChange
l 10 --
+I
1
-
10 4!
to I ...*;
"
,.. ..
to +I
10
Logical message to
Paoner Number
Partner Functlon
ENTER DIRECTION(1- OUTBOUND), LOGICAL MESSAGE(C0SMAS) AND

PARTNER NO(RECE1VER).
EXECUTE IT.
--" - - a + n r A @a@ ;E~,$>> &%A
"
@fV**" - -"
2C
SAP
Page 12 of39 By Ganapati Adimulam

4
Ph No :+9140 -65976727, Cell NO : 9948444808,98490 34399, wmv.emaxtech.corn
4
4
We Never Coinpromise In Quality. Would You?
Notice that the IDoc is Successfully Generated and Dispatched.
DOUBLE CLlCK AND

CHECK DATA AND STATUS RECORDS.
CONGRATULATlONS ! OUTBO SUCCESSFLTL.
TESTING TIIE
GO TO THE RECEI MAKE S U m THAT IT IS POSTED

SUCCESSFULLY.
L
'
%
ap?t **.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w\wv.ernaxtech.com
ENTER DIRECTION(2 -INBOUND), LOGICAL MESSAGE (COSMAS) AND
PARTNER NUMBER(SEND0R) .
EXECUTE.
NOTE : THE COST CENTER POSTING CAN ALSO BE CHECKED THROUGH

KS03CDISPLAY COST CENTER) FOR THE EXISTENCE OF COST CENTER.
eMax Tecllnologies,Ameerpet,Hyderabad
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.ernaxtech.com
- the Master Data Via Standard IDocs
5. Distributing
We Never Colnprornise I11 Quality. Would You?
2) Get/Fetch/Yull Whole Copy

Request RECEIVER
SENDOR
Response
NOTE :EITHER REQUEST I RESPONSE ACROSS THE DISTRIBUTED

SYSTEMS IS ALWAYS Via MESSAGE TYPES AND IDOCs.
NOTE :THE SAME IDOC ALEREQOl IS USED TO REQUEST ANY
APPLICATION DATA(1DOC).
/ <
v'
,& 4
NOTE : WE CALL REQUEST AS FETCH AND RESPONSE AS SEND. 4
RECEIVER
END -COSMAS'-+, $
t, -,'
Application Message ' <-- IDOC ~ype Outbound
&: *.; '
%>. X *.
Type .?, I Program1 Program1
Materials
Fetch MATFET ALEREQOl BDll MATF
Materials
Send 'DEBMAS 1 DEBMAS01,02,. .. BD12 DEBM
4
Customers
ALEREQOl BD13 DEBF
1 Customers
Send Vendors CREMAS CREMAS01,02,... BD14 CREl
Fetch CREFET ALEREQOl BD15 CREF
Vendors
COSMAS01,02,. .. BD16 COSM
Centers
Fetch Cost COSFET ALEREQOl BD17 COSF
I Centers J
Page 15 of 3 9 By Ganapati Adimulam
Ph No :+9140 -65976727, Cell No :99484 44808,98490 34399, w~~~.emaxtech.com
4
CONFIGURATION REQUIRED :
FOR COSFET:
INBOUND Partner Profile Distribution Model

OUTBOUND Partner Profile
FOR COSMAS
Distribution Model 4
OUTBOUND Partner Profile
COMPLETED IN SEND COST

WHOLE COPY ) SO THAT IT IS ENOU CONFIGURE
FOlP COSFET 1.E FROM RECEIVER TO SENDOR.
NOTE :COMMUNICATION SETTINGS ARE ALREADY

CREATED PROM% SENDOR TO RECEIVER AND THE SAME
s w
COMMU~~ICATION SETTINGS ARE REQUIRED FROM

RECEIVER(BIO)
.T2 T&SENDOR(SOO). 4
b
."%i& .$
-
1 .EXECUT$S"AEE"TO DEFINE AND LINK THE LOGICAL
SYSTEM TO THE CLIENT(SALE).
2. MAINTAIN 1WC DESTINATION TO SENDOR(SM59)
3. CREATE A PORT TO SENDOR SYS.(WE21)

3
eMax Technologies,Arneerpet,Hyderabad
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~w.ernaxtech.com
OUTBOUND CONFIGUIUTION FOR COSFET AT RECEIVER :

LOGON TO RECEIVER(810)
A) Maintain Distribution Model: Create the Distribution Model and Add the
Message type to be transferred.
LOGON TO RECEIVER ( 810 1

A) MAINTAIN DISTFUBUTION MODEL AND ADD MESSAGE TYPE
EXECUTE BD64 AND Click On Change - pi
4
li lulodel views I
PL N O shorttern exlsts
BBP-DII NO snort text exists
BC61 9-300 N o shnrttrx* exists
BELCO NO short text eXlstS
BlT300-BP N o Shorttext exists
CONS0LIDC.T N u shorttext exlsts
DIZ-ID3 N o short text exlsts
DlZ-IDBCLN N o shot? text exlsts
EBP3DO-R3 NOshorttext e x ~ s t s
HR-ORG-SEM NO shortteld exlsts
. N o short text exists
text exists
. .
4
-
/ 1
*
" @ 'S 8" Fllter model ollsplay -Create model view

. . ;. -
2 -
lirid BAPI A* 4pe
kcd t-n~?-;sage
".-"
.
A
- +.
.ni ir 's%w" ,urn,.-- ,, *uc, P
.s
- ;
? -m-,n 7
--
7
/ _-__i___
01sttil)ut1otiMudel
--I__----__-
' Descript~otiltechr~ical
name
~
V Rloolel views
AL No short text exists
BBP-DII . No short text exlsts
D ~ j l t 23-1 BC619-&OU blo short text exists
i dl'..
For All tvlaster Data Distt~but~ons !=
Create niodel view j

Click On -!'-T-Y-Y AND Enter Short text, ical Narne(Distribition
Model), ENTER
SAVE it.
eMax Technologies,Ameerpet,IJyderabad
P h No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~w.emaxtech.com
Note :Now Distribution Model is Created . So that we Can use the same
Distribution Model to Send any the Message. No Need to Create a new
Distribution Model for each Message Type to be Transferred.
Note : Distribution Model Acts as a BAG to Carry the List Of Receiver Details for
all Message Types J
For Each Message type to be Transferred :

Select the Distribution Model andclick On Add Message Type 1
-0,Add
. message iype i
, No short text exists
b
p
z
r J ~ - - ~ ~ ~ ~
zi
a;:,?; ;3-:;;3
P-DII . No sliort text exists
61 9-800 . No shotttext exists
b. g
=-:,:.I:; L C 0 . No short text exists
B t$g ~ l - ~ ~ l ~ i - ~ - ~ 300-BP . No short t e d exists
p Bz i::~~:,~!~(:;~;~hy~ NSOLIDAT. blo short text exists 4
p 3: >: ; -?,""; ;,
p F& c<,:z,-ic;:::JJ.,i
p. 22 ~ ~ j ~ : ~ ~ . c ! - , + : P3Un-R3 . No short text exists
b 8; +jfi-:;,;-! .:-:&j OFG-SEM. Iflo short text exists
ga!
Y -
1s . No short text exists
b
D
z -<:yi$i
gji,~;~-:;js
21 5 . No short t e d exists
RCUS . No short text exists
p
['/
zz :~~~-~[.,ij'~q
>SH-SI,J"$.;:'
B-BUYER . No short text exists
B-SUPPLY. N Oshort tm< exists
p. 4
g2;s
D ~ s j e s s~i::;:
j BSYSTEMS. No short text exists
p 24 1:j53j
:+, IS . No short text exists
14. , No short text exists
p $4.:~: . No short text exists
b ;, ..,.q r)..
# S,.,,q ... .;i i:
*:-, 7 r,
c.5 4.53
D SF:!.. $;h:,?,e:: -Ei;Jzlp;o
C, 3H3..:.,:3:$ i1,f;'J ,<..? ;ij:$
PROVIDE SENDOR, RECEIVER AND MESSAGE TYPE To be Transferred.

P h No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~vvr..emaxtech.com
We Never Compromise I11 Quality. Would You?
ENTER AND SAVE it.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, wmv.emaxtecl.com
5. Distributing the Master Data Via Standard IDocs 4
We Never Colnpromise I11 Quality. Would You?
Note : Repeat the ADD Message type Steps for each message type to be
Transferred.
B) Maintain Outbound Partner Profile(WE20) :
Note: In the Outbound Partner Profile, We Maintain the Below Information.
Whom to Send What to Send Medium Of Data Mode Of Dispatch
Tranlffer
Partner Message
(RECEIVE Type +
R) IDoc Type
Note :We always Create Only file for each receiving(Par and One
Entry for each Message type we r.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emaxtech.coni
We Never Coinpro~niseIn Quality. Would You?
Enter Partner No (Receiver Lo ical System Name) and SAVE it.
SAVE IT.
Same Profile, every time WE REQUEST a new Message type.

i
NOTE : INFACT THIS PARTNER(SEND0R) IS ALREADY CREATED AS
THE INBOUND PARTNER PROFILE FOR COSMAS. SO WE CANNOT
CREATE THE SAME AGAIN AND NOT KEOUIRED ALSO.
, .
. \

For Each New Message to be Requested From the Same Partner (SENDOR):
From the Same Screen - WE20

Select the Partner and Click Create Outbound Parameters
&Q Position
50000000 ALE administrator
English

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, wvrw.ernaxtech.com
We Never Compro~niseIn Quality. Would You?
NOTE :ALL THE OUTBOUND CONFIGURATION SETTINGS

ARE COMPLETED. We Can Request the IDOc But it Fails in ,
Posting the IDoc in the INBOUND Sys. So Before We Request for
the Cost Center Master Data ,it is better to Complete .the INBOUND
Settings also to TEST the Complete Cycle.
Page 23 of 39 By Ganapati Adimhlam

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~yvc..emaxtech.com
We Never Com~romiseIn Oualitv. Would You?
MAINTAIN INBOUBD Partner Profile (WE20) :

LOGON TO SENDOR (800)
CREATE PARTNER FOR RECEIVER, WHICH WAS ALREADY CREATED AS

AN OUTBOUND PARTNER FOR COSMAS AND NOW ADD INBOUND
PARAMETERS FOR COSFET.
EXECUTE WE20 ,Partner Type as LS

SELECT THE PARTNER AND CLICK ON CREATE INBOUND PARAMETERS.
R

eMax Teclinologies,Ameerpet,Hyderabad
Ph No :+9140 -65976727, Cell No :99484 44808,98490 34399, wm.emaxtech.com
We Never Co~nprolniseI11 Quality. Would You?
ENTER MESSAGE TYPE ODE(C0SF) AND

TriggerImmediately.
I
NOTE :BOTH OUTBOUND AND INBOUND CONFIGURATION

SETTINGSARE COMPLETED. WE CAN TEST THE COMPLETE
PROCESS OF REQUESTING THE COST CENTER AND
RECEIVE IT AND POST(CREATE) THE SAME IN THE
REQUESTING SYSTEM.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, wmv.ernaxtech.corn
We Never Cornprolnise In Quality. Would You?
SO BEFORE CREATING TIIE~ZOST

CENTER, CHANGE THE LOGICAL
SYSTEM NAME OF CLIENT 800 FROM SENDOR TO
4

4
4
Master Data
.. . . .. , -
?---..--
Cost Center 786 E U.AX TRAII'.III.IGS
Controlling Area ICl0U CO Europe
Valid Ftorn 11 . 3 2 2003 to 31 . I ? . 9959
. ... .
Basicdata \ Contt.01 3 Teii~plates Address Commui~ication i: Histoty , ; *
.---"
Efr~lWTRAININGS
Description SAWTRAINING DIVISION
-
" " ---- --". - - ----
'1
-"--a " "
Basic data , /
[%o~~~sponsible tulr.Rarna Rao
1
Department
I
j
a
Cost Center Cateyor>{ E Development

/ Hierarchyarea H - AC41 0 Traininy AC410
! Company Code 1000 IDES AG
/ Business Area 9900 Corporate Other
1 Functional Area
8 Currency EUR
"
Profit Center
SAVE it. Cost Center 786 is Created in 800(SENDOR).

Now Let us request the Cost Center 786 From RECEIVER Sys and also Make sure
that it is Received a t RECEIVER and Also Posted (Created) Successfully.
Before Request, Check the Cost Center at RECEIVER and Make sure that it is not
available(Created ) And After Requesting it should be Created Successfully.
Execute KS03 At RECEIVER System(810).
ENTER
.
-... -
Display Cast Gsnter: &3Efi8I Screen

eMax Teclinologies,Ameerpet,Hyderabad
Ph No :+9140 -65976727, Cell NO : 9948444808,98490 34399, w~w.emaxtech.com
We Never Coinproinise In Quality. Would You?
D i ~ p i ~8 Q~ S $C@&@gX: Screen
i lvlaster Data ,
EXECUTE BD17(Request Cost Center) a&RECEIVER Sys(810)
EXECUTE

We Never Compromise 111 Quality. Would You?
$
@
r^--.---------.--------.--------------.---.---.7.-----.------...-----F..
2.st,,,,,............DI,.,........created - - - - -.,I?ssa,e
-- - - .- - - .-fur *
,,,
- - - - - . .- - - - - ... - -,,,,As;
- - .- .- - - - - .
Check For the Successful Cost Center Creation ,If Not Created then Check the
IDoc Status to identify the reason to fail.
EXECUTE KS03(Display Customer) at RECEIVER Sys(810)
D#.sp#ay
C-@ Ce~&@@ -z
fm#Z8a# S~reen
Master Data
Page 30 of 39 By Ganapati Adimplam

eMax Technologies,Ameer~et,Hyderabad
Ph No :+9140 -65976727, Cell No :99484 44808,98490 34399, mw.emaxtech.com
"
-"
-" -
-
"
-"
- ----- "
-
" --*--
7
Etl~1.4XTRAININGS 1
1
I
Description SWd TRAI NI Id G DI'JIS ION
,----- -7-----------
Business Area Corporate Other
Y
V

We Never Coln~rolniseIn Oualitv. Would You?
Summary Of Fetch Cost Center :

The IDocs to be Exchanped(Transferred) between SENDOR and RECEIVER-
Which gives the Actual Status Of IDocs
1)Request COSFET - Status Code(03-Dispatch OK) at RECEIVER.

2)Post COSFET - Status Code (53 - Posted Successfully) at SENDOR. 4
3)Send COSMAS -Status Code(03-Dispatch OK) at SENDOK.
Current slatus 03 OX.

Basictyl~e RLEREQOI Baslt $e llEREQB1
Patrierno. REGElYER
Paltner no. SENDOR
RECEIVER , Direction - 0 1(Outbound). , SENDOR, Direction - 02(INbound).
3)SEND COSMAS (Cost Center) 4) Post COSMAS (Cost Center)

EXECUTE WE02 For COSMAS at Execute WE02 For COSMAS at
RECEIVER(81O),Direction02(INbound).
I

Ph No :+91 40 -65976727, Cell No : 99484 44808,98490 34399, wl~v~.emaxtech.co~ii
We Never Comprotnise In Quality. Would You?
3) Change Pointers (Send Changes Only) : h
Send Changes Only (Change Pointers Technique)
SENDOR RECEIVER
For any Change in Master Data

6
Tables Used 4
CDHDR - Change Doc.Header

-
CDPOS Change Doc.Items
BDCP -
Change Pointes
-
BDCPS Change Pointer
Status

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, m~w.emsxtecb.com
5. Distributing the Master Data Via Standard IDocs 4
NOTE :
To Generate Any IDoc From Change Pointers technique,
The Set of tables to be accessed is same i.e BDCP,BDCPS,CDHDR and CDPOS.
So that Only One Outbound Program(RBDM1DOC) is enough to generate any
IDOc(Customer,Vendor,Material.. .) from Change Pointers.
NOTE :
Outbound Program RBDMIDOC(Tcode - BD21) ,Checks for the Change
Pointers for the given Message type in BDCP and also the status in BDCPS if
Changes are not yet Sent then it generates the IDocs only with those Changes. And
After Generating IDocs it also Updates the Status of Change Pointers in BDCPS .
Because this program always make sure that Only one IDoc is generated with all the
changes until we execute this Outbound Program. Fy
C
.
Change Pointers Specific Config;uration : 4
These Configurations are required Only a t Outbound
Generic Outbound Configurations
Such as Distribution Model - BD64
Outbound Partner Profile - WE2
No Change Pointers Specific Settings are requ stem, Because IDoc

is Generated at Outbound System by consider nters and where as
Inbound as Process the IDoc as it is.
LOGON to SENDOR Svstem
1) EXECUTE BD61, Activate Change Pointers Globally(General1y).
] Activation status / "

--------------------
6
~
/
- I
i1p Change pointers activated - generally
: ~ ~ ~ ~ - ~ * L ~*--?
i
~ ~ . ~
I ~ ~ ~ ~
....._.......----,-....----------------------------------,---------m----------------------------
Select the Checkbox and SAVE it. 4

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~yw.emaxtech.com
We Never Coinproinise I11 Quality. Would You?
2)Enable Change Pointers for a Message type
EXECUTE BD50.
Check the Messag

i
e to be Written(BD52)
Note: For Standard uch as Cost Centers, Material,
change Pointers are written.
If you are happy with those fields, you can SKIP this Step.
If you are not interested with certain fields we can ignore by deselecting and new
entries can also be added .
Note :I n Realtime, Generally We Skip this, Because SAP Already includes all the
Mandatory Fields.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~wv.emaxtech.com
We Never Coillpromise 117 Quality. Would You?
EXECUTE BD52 to activate the Change Pointers for Message type and it's Fields.

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~w7.emaxtech.coni
4
We Never Compromise I11 Quality. Would You?
,
New Entries
To Add Additional Fields - - AND A d d ,
To Delete, Select the Entry to be deleted, .
Testing :
EXECUTE RBDMIDOC Pro,oram
CASE 1 :Execute for the ~ i r stime
t
Note : Notice that there are many IDOcs generated when we run the Program
RBDMIDOC for first time.
CASE 2 : liun the Program with No Changes in Cost Center Master Data
Run the Same Program Again ,Since All the Changes are already sent, No IDOCs
should be Generated.
Page 37 of 39 By Ganapati Adimblam
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, ~vww.eniaxtech.com
EXECUTE RBDNIIDOC Program
c#"@agjga!g #fD@G Ty#3@ Po~#~~@Ts
f ~ a r f 8 CF#B#B$~
Note :Notice th IDOCs are Generated.
Change Some the Data Of enters ,and Execute

RBDMIDOC and Make Sure t Ocs are generated for the
Changed Cost Centers. ',
Execute KS02 to Change Cost Centers

C h a r q s Cos$ C@b"z$er:# ~ i & # a S
P ereera
Master Data
C n s t Center PEE t?

Ph No :+914O -65976727, Cell No : 99484 44808,98490 34399, w\nr.emaxtech.com
-w ) m I c#3a9$w& < ; e # a g e y z B&#*#G
SG#&*#&
Description
on R e s p o n s i b l e Mr.Ganapati kdirnularn
Department
C o s t Center C a t e p o w E Development 1
Hierarchy a r e a H-P.C410 Training A C 4 1 0 !
1
Company Code 1000 IDES A G
B u s i n e s s Area 9900 Corporate Other
Functiortal A r e a
EUR
1 master lDocs set up fur rnessage tqpe COSlvlAS
CONGRATULATIONS! ,One IDOC is Generated Because Only One Cost Ceuter

is Changed. To Check IDOc Contents, Execute WE02lWE05.

6.Filtering
We Never Compromise in Quality. Would You ?
IDoc Filetering; :
Filetering a t IDOc Level Creates a Communication IDoc in which an Object's views

are filtered out, based on the filters specified in the Distribution Model(BD64).
Business Scenario : A Company has 10 Individual Business Centers(Company

Codes). Each Company Code Operates individually on its own SAP System. When
ever a customer to be Created, all Company Codes need the General Data of the
Customer and Company Code is to the Specific Company Code.
Ex : Company
Since Customer is from Company Code 1000, Distribute the Company Code
000 Sys and all other Information to all the
Note : In this Filtering, When a Master IDOc is Created, the IDoc

Consults the Distribution Model and Determines whether any filter
Objects are Specified for a receiver, If So, the Value in the filter
object is Compared to Values in the Master IDoc's data records. If
the value doesn't match, the data record is dropped in the
Comminication IDoc for the Receiver.
I I
Note :SAP Already Provides some filter groups for each Standard Messages type,
so that when we found the filter object for the required Message type, it is enough
to Provide the Filter Values at Distribution Model Level.
Page 1of 21 By Ganapati Adimulam

6.Filtering
Noie: . .ct;... 'i'ransfer the Company Code Information, Only when the Customer is
Crealc. . i:. <:a:npany Code 1000.
Con 1': .,-r!-;-:i !ion required in Only at Distribution Model :

--
P-DII . No short text exists

61 9-800 . No shorttext exists
300-BP . No short text exists

NSOLIDAT. No short text exists
Z-ID3CLN. No shorttext exists
ORG-SEtvl. No shorttext exists

. No shorttext exists
RCUS . No short text exists 4

0-BUYER . No short text exists
0-SUPPLY. No shorttext exists
S . No short text exists
BSYSTEMS. No short text exists
v1S . No short text exists
. No short text exists
V . No short text exists
del Which is already Created and Click On Add Message
Pagc 2 ,I;
.2 .
- <
By Ganapati Adimulam
--
ehlax Technologies,Ameerpet,Hyderabad
;-;. i:u :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emaxtech.com
6.Filtering
We Never Com~romisein Oualitv. Would You ?
DEBMAS -> Message type For Customer Master.

I ~ ~ s ~ r n -model
~ u t ~~k a ~ g~e d
a m

6.Piltering
y ;
?. - .
~Jl',.'lSlOn Dlvislon :,d
IG.1
-
E;.sles Organization Sales ~ r g
I., . : Cli.;trihution Channel Dlstr~butlo&%
Click I
..
: ;:.3L1;-t Rows and Enter Value Company Code GL1000(1000)
. . By Ganapati Adimulam
Pag: -,,,.
A
-
-
eNlax Technologies,Ameerpet,Hyderabad
:.: P:,) :+91 40 -65976727, Cell No : 99484 44808,98490 34399, ~7nv.emaxtech.com
6.Filtering
We Never Com~romisein Quality. Would You ?
SAVE it.

6.Filtering
2 . Maintai:: -;ie Outbound Partner Profile, for Message type DEBMAS
EXECUTE M'E20 ,Select the Partner type LS -> RECEIVER->

Create 0ul:zoitrld Parameters
Page 6 of 2 : By Ganapati Adimulam

eMax Technologies,Ameerpet,IIyderabad
2::Sib :+9140 -65976727, Cell No : 99484 44808,98490 34399, ww.emaxtech.com
6.Filtering
We Never Com~romisein Oualitv. Would You ?
SAVE it.
Testing :
Create a Customer in Company Code 3000.
Execute XDOl to Creating Customer.

Ph No :+9140 -65976727, Cell No :99484 44808,98490 34399, www.emaxtech.com
6.Filtering
We Never Conlpromise in Quality. Would You ?
Execute BD12(Send C
Send Customers
EXECUTE IT. 4
Page 8 of 21 By Ganapati Adimulani

eMax Tecl~nologies,Arneerpet,Hyderabad
6.Filtering
We Never Comvromise in Oualitv. Would You ?
ENTER
$ ,
\ \A,
Check for the IDOc : -4".

- \,
\
, , !W
Executer ---"
,.I"wWE05
""* - -,
"
,
" -" - - ,. ,, , , - ,,,~~-,, .,, ,,,, *-
\
,,,,,," ,,, , ,,, , - ,. , "

6.Piltering

eMax Technologies,Anieerpet,Hyderabad
Ph No :+9140 -65976727, Cell NO :99484 44808,98490 34399, mw.ernaxtech.com
6.Filtering
ENTER
Check for the IDOc Status : \
Moc Iist

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, ~ ~ ~ ~ . e r n a x t e c h . c o m
6.Piltering
We Never Comwromise in Oualitv. Would You ?
Segment Filtering
Creates a Communication PDBc in which Segments of a Particular type are
Completely removed from the IDOc.
Note : The Difference between Segment Filtering and IDOc Filtering is In IDoc
Filtering, Segments that do not contain relevant data for a receiving system are
Filtered Out where as in Segment Filtering, a Segement of a Particular type is
Completely removed from IDoc.
Note :In Segment Filtering, For Each Sendor, Receiver and

Combination ,We Can Specify the List of segments to be moved. When a
Master IDoc is created, it consults the Segment filters ted
Segments to create the Communication IDoc for a rec
Configuration Required :
Execute BD56 /;;-
i~
ENTER
-* ,
9
-, ,, , ,,, , , , , , ,,,, , ,, , , ,, .
I
Cka~sgeView "S@pnentFiBep-s":
Owmew
%
9 [EeGE z i/-f?~ B.
New Entries (F5)
;&$I
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
rr*n,
.aD .
. . . . . . . .
.-------.----.------. .... .... . . .
I
. . .
. .
;Message
---------------- Npe;
- -.. ....... -- ---- . .. . . .. . . . . . .
--. . .--, . . --.-.,, -. -...,.
. .
-.v......--.
,. *
.
- . ,
_
,
..
i
..
< .
.
-..
i i - l
L
.
. . y.; ....... .-.-.- .
Segment Filters,,
.
- -- . -... --- . -
..
-.--... -.
New Entries

P h No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emaxtech.com
6.Filtering
--.-wv:-.- - ------ -"-.-- --- --------.----
-" ----
--w,--w-----"
4
M e w E ~ ~ ~ E - $ @ C&F@P~~-@W
SZ OF i 4 d d ~E?@%~&&s
~$
4
Note : Make S R and
RECEIVER in the System where
SAVE it.
Note : Make S Profile is Also

Maintained.
Here Segmcnt pped behveen SENDOR and

RECEIVER.
Testing :
Execute BD14 (Send

eblax Technologies,Ameerpet,Hyderabad
Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, wuw.emartec$.com
6.Filtering
Here Vendor 1000, exists in Company Code 1000. But the Company Code Segment
is dropped in the Segment Filtering.
Y_ " :- -- " "--" . -

k'b\
Check for the IDoc '\

6.Filtering

eMax Tcchnologies,Ameerpet,I3yderabad
6.Piltering
Reduced IDoc Type

This Technique allows to the field level i.e we can specify the list Segments and
Segment Fields allowed to the receivers.
Scenario : Two Systems A and B ,decided to Maintain the Standard Price for Material
master Data Locally on their Systems. They want to receive very limited data from the
Central System. So that We Can Reduce the Standard IDoc to the Reduced IDoc with the
Required list Of Segments and Segment Fields.
Note : The Reduced IDoc type gets a New Message type and the the Reduced IDoc type
is defined from the Standard IDoc by Enabling and Disabling the List Of Segments and
Even fields .
Note : In Both Distribution Model and Outbound Partner

Message type should be Configured.
1) Analyze the Data to decide th Included.

Ph No :+9140 -65976727, Cell No :99484 44808,98490 34399, www.emaxtech.com

Emax Volume 4

Uploaded by

Copyright:

Available Formats

Emax Volume 4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Emax Volume 4

Uploaded by

Copyright:

Available Formats

INDEX

SNO Chapter Pages

4 Outbound & Inbound @Y2- .+F22 ,

5 Distribute Master 9Byfg2yia @

Standard IDoc %, *4&$ j

7 Trouble Shooting & 07

ALE (Application Linking and Enabling)

A distributed process is one in which part of a business process(Sa1es) is carried out on

Need for Distributed Process:

. It was inlpoi-tan: from

SAP Distributed environment:

Integration with non-SAP systems: ALE architecture allows third party

ALE may also reduce costs, in particular costs of

entire company is affected

not involved and need no tra

known to all ass you to immediately trigger an IDoc sent to

Page 2 of 2 By Ganapati Adimulam

Scenariol: SAP - SAP

Note : Since Both the systems are SAP Systems, they ca

Note : IDoc is Collection of Segments AND Each segment is collection Of Fields.

Page 1 of 11 By Ganapati Adimulam

/DOC Design Guide Lines(Syntax Rules)

Analyze the Application Data to be transferred Via IDoc AND

Identify the List Of required Segments

Decide the Parent & Child Segments

Decide the Minimum & Maximum No Of Repetitions of each Segment

Decide the mandatoryloptional segments

Seginen.ts are reusable

- Segment Definition (versiou dependent)

The last 3 characters is the versioil of the segment

Data Types Description

/DOC Run-Time Components

An IDOC is an instance of an IDOC Type

At run time the following events occur

One control record is attached to the IDOC

Segments are translate into data records

A unique IDOC no. is allocated by

I Control Record 1 I Data Records 1 I Status Records I

IDOC Number Links

Page 3 of 11 By Ganapati Adimulam

1 ElKNBl 1 KUNNR, BUKRS,ZTERM,. .. Customer Company 1

IDoc Creation Is a TWO Step Procedure.

1) Create the required Segments through Seg

Stel, 1 (Segment Creation ) in Detail :

Execute WE31 and

Page 4 of 11 By Ganapati Adimulam

SAVE it and BACK.

Edit -> Set release.

Page 5 of 11 By Ganapati Adimulam

2"dSegment : Customer Company Code Information

Page 6 of 11 By Ganapati Adimulam

SAVE ,BACK and Edit -> Set Release.

Step 2 (IDoc Creation ) in Detail :

iCreate a s coPj2 c o p y from

" L--.. --->-

Person responsible SAPUSER

I lDoc For C u s t o m e r Master

Page 7 of 11 By Ganapati Adimulam

( c r e a t e s e g m e n t ... hiit it+^^)(