emax volume 4

(1)

(2)

(3)

INDEX

SNO

Chapter

Pages

1 Introduction

02

2 IDocs

&

Message Type

.

,:(I

.+

1

-'*

3 communication Settings~

s,p,, .- ,,%-

-

1 2

*-

4 Outbound

&

Inbound

4;.

4$$?6',,

@Y

4 zqw22

2-

..+F22 ,

5 Distribute Master

9

Byfg2yia

Sp,% a

@

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

Standard IDoc

%,

,-c f ..." , -5-

6

L u-- -

21 Filtering

zz%%

. L ~ ~ ~ ,

,* .a - i -, r e > - r *il

7 Trouble Shooting

&

07 Recovery

8 Custom

IDocs

30

1

, .A . . A . , . - - C ~ I T ~ ~ D R I S E S . XEROX Floc No: 40, Gayatlui Nagar, Behind HUDA,

SOFTWARE INSTITUES MATERIAL AVAILABLE

(4)

(5)

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.

( O R )

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~ronized after 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

(6)

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

(7)

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(S AP/Non-SAP).

eMax Technologies, Ameerpet, Hyderabad

(8)

2. IDocs

&

Message Type

in Detail

/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

components.

Seginen .ts are reusable

- 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 CHAR

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, www.emastech.com Description Character String CLNT CUKY DATS Client

Currency Key, refrenced by CURR fields

(9)

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

1

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

IDOC Number Links all types of Records

(10)

2. IDocs

&

Message Type in Detail

IDoc Creation

:

IDoc is Collection of Segments

Each segment is collection Of Fields.

Ex : IDoc : DEBMASOl (Customer Master)

-

Standard IDoc.

1

ElKNBl

1

KUNNR, BUKRS,ZTERM,.

. .

Customer Company

1

Se ment Name

1 i

1

Code Details

1

5 (

Etc..

.

I E l K N A l M , KUNNR, I

Note : All the Standard Segments starts with E l it is recommended to start

the Custom Segment names with Z1. IDoc Creation Is a T W O 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).

Customer General Data

Stel, 1 (Segment Creation ) in Detail :

Execute WE31 and ElKNBK

Page 4 of 11 By Ganapati Adimulam

eMax Technologies, Ameerpet, Hyderabad

Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, ~~ww.cmaxtech.com

--

(11)

j Segrnentfiipe attribl~tes , '

+----..- I II I - I

8

; Segment ffpe Z I Kf4AI

r?

- Qualified segment

j ---,

:Short Descriptiuni

:I :----_r---.--- Custorner General Data

SAVE it and BACK.

Edit -> Set release.

(12)

2. IDocs

&

Message Type in Detail

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"d Segment : Customer Company Code Information

(13)

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 f I i Create a s coPj2

I

c o p y f r o m I . Create s u c c e s s o r S u c c e s s o r o f ---- -" - - " -- -- --- -- ---- - "--- "

I

,--&.4

- "

- -A*--A- " L--.. --->- ' " _-- --- _- 2 / "4- A" --- "b - ..- "-. "&. Adrr-iinistrat~on r '

F---

- -- - --- ,' P e r s o n r e s p o n s i b l e SAPUSER

/

P r o c e s s i n g p e r s o n SAP U S E R I - - V" - 2 > -**--

-

" ---.

-

---- >-""- --*"--.."- -"-.---*-a -s D e s c r i p t i o n ,,/" $1 -- -- " "

I

lDoc For C u s t o m e r Master

(14)

2. IDocs

&

Message Type in Detail

Select Create new and Provide the Description then Continue (ENTER).

[B

pJ,

?& @ ~2 Pz" <Q

-2

-

( 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

(15)

We Never Compron~ise In Quality. Would You?

ENTER.

" - e 9 of 11 By Ganapaii Adimulam

eNIax Technologies, Ameerpet, Hyderabad

(16)

2. IDocs

& Message

Type

in Detail

We Never Coluprolllise 111 Qi~ality. Would You?

a n c e l 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

(17)

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

Z 1 HL Home Loans

ZlPL Personal Loans I

segment

I Z I EL

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 a t the receiving System. Description

Entertainment Loan

1

- p~

IDoc

1

Message Type

ALEREOOl

1

MATFET (Fetch Material)

Note : The Same IDoc ALEREQOl is i s e d to fetch any Master Data and Fetching

Each Master Data through a Different Message Type. ALEREQOl

ALEREOOl

DEBFET (Fetch Customer) CREFET (Fetch Vendor)

(18)

(19)

ALE Communication Settings

:

Note : Con~munication Settings 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 Clients : RECIEVER 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

(20)

3. ALE Communication Settings

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

(21)

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~gn Clrent to Logical System

Convert Loaical Svstem N a m e s in Asslication Tables

(22)

3. ALE

Communication Settings

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

(23)

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.

(24)

3. ALE Communication Settings

4

Note : Now the Participated Clients 800 as named as SENDOR and

810 as RECEIVER.

Address) and the Logon Details of the Receiver LOGON to SENDOR Client(800)

EXECUTE SM59. 4 Select RECIEVER Client : 810 SENDOR Client : 800

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

.5!

Note : in the RF'C Destination, We Provide the

receive^-8s

Details(1P

Logon Details

+

4

(25)

(26)

3. ALE

Communication Settings

We Never @ompromise In 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

(27)

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

\1

ogon

Click On Remote Logon *-"---"

- - - from the Same Screen.

eMax Technologies, ~ k e e r ~ e t , Hyderabad

(28)

3. ALE

Communication Settings

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

Connections via ABAP14 d r i v e r

I

Page 10 of 12 B y Ganapati Adimulam

(29)

.

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.)

4

art Of Communication Settings)

dium of transferring Data.

Port ( Transactional RFC).

LOGON to SENDOR : EXECUTE

-

WE21

(30)

3. ALE Communication Settings

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 ~ ~ ~

(31)

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~nunication IDocs 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 fro111 the Outbound Partner Profile. Asynchronous

eMax Tecl~nologies,Ameerpet,Hyderabad

(32)

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

I

Communication Layer

I

ALE Inbound Partner Profile

IDoc Inbound Progl

Process Code

---

DEBMAS DEBM CREMAS C R E M l C N l MATMAS MATM 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).

(33)

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 a r e 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

(34)

5. Distributing the Master Data Via Standard IDocs

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).

2

J Maintain the Distribution Model ( BD64 )

3

J Maintain Outbound Partner Profile ( WE20 )

A) Maintain Distribution Model in Detail: Create the Distribution Model and Add the Message type to be transferred.

i ? % $ , Z

EXECUTE BD64 AND Click On Change

14

. -

. :. .

.

121; a! F p:. r l l l e r r n o d r l . display . < : : : ...iV?-.!I :,.!:! r>:S: x., ' ,,. ,,. .

-,---w?-?v .. _...- ~ - ~ - m . , . - _ _ - . - , - - " _{. .} _,.--,---- ---,--. _{. . .} ""*

s ! d + i ~ , p . ~ ~ ~ i s ~ ! . . v ' a n q e c t m o a - . - /Descr=nnical name ~ u s l n e s s owect -.

2 n Model vlews : 0 % ,;:. , A L . N o Short f e n exlsts ( p % .*.;. .::< BBP-011 NO short text ~ X O S I S B C S ~ 9 - 8 0 0 . NO shortfextenists R E L C O . N o snon l e d exists 4 bc I rz -Ai: . < ;I,, .,.. 81T300LBP N O s h o r t l e d ex1SlS

i % ::..;:::':.i:,:a :CONSOLIDAT. N O short lent eesls

! b a :>I .:;: D l L I D 3 NO snort ted exists L> .. t -' .:;: .: : D < Z _ I O P C L N . N o shortlext eilsls

iEBP3OO-R3. NO shorttext exlsls H R - O R G - S E M N o shorltextexisls

L I S NO 5 h o r t l e x I e a ~ l s

. . . . iOSB-SUPPLY. N O shod l e d exlsls P F S N o snort text eiAsls

2 b % .:::.. ,!.: , s. : ! :",,': :SUBSYSTEMS. N O short l e d exlsls

i u z ;..?... WlvlS N O shorttext e ~ i s l s ! O X . , . XI . r10 short l e d exists 1 ,::<, i Z 8 " N O S l l O l l t e k f exist* 1 % ::.;,( . : < > . , : r > y , ! . . iE2W-lDES 1

,

::; :, , ;.: .... :,: 'DE3-WBi\ i x i .... ., ..i... ::.- . :;. i D U 3 . b I D 3 1 L> :..&.

.

,.,,< :;,,

.

..,... t , :; ,.., ::,: ,;..,; E B P I O - R 3

eMax Technologies,Ameerpet,Hyderabad 1

(35)

NO shod t e a exists

XI NO shorl

.ZBV N o s h 0

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.

(36)

5. Distributing the Master Data Via Standard IDocs

We Never Co~npromise In Quality. Would You?

For Each Message type to be Transferred :

1 a

Add message type j

Select the Distribution Model andclick On Add Message Type --

A L . N O Shorttext exists BBP-Dl1 N O ~ n o r t t e x t exist5 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. NO short 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 .No short l e d exists XI . N O short lexi 8x1~15 ZBV NO Shontexi exists BZB-IDES

DE3.KABA DH3->ID3

Y ?- FFllter momel Olsnlsy 5 Creele r n O G s l u l e w O Ad0 BAPI Add mes4s.e hpa

, -A

,.--.---- "A L- -- __-___--- --

ooctnbuslen ~ ~ a m , ~ e : c t ~ p t i o n , t e e n n ~ c i . ~ "rme B"e,n..I O b l S S l

-? Moue8 "lBWS

A L N O short Lad e x , s , s BBP-DII N O Snortten e x l l l s 'a0019_800 N 0 5non,en ex1515

SAVE it.

(37)

We Never Comprolnise 111 Quality. Would You?

B V Filter model display O create modelvlew O ~ d d BWI add messagevpe -

A : - 2 - . . : : - d 2 - ----." --- ..-2r

1 Dlstrlbutlon Model D e s c r ~ ~ I ~ o n I t e c h r l ~ ~ a l name 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 NO short text exists :HR-ORG-SEM. No shod lext exists

LlS . NO sliolttexiexists LO215 .NO shorttexiexosts 'MARCUS No shorttext exists

OSB-BUYER . No shorttexi exists OS8-SUPPLY. No sliorttent eHsts

PFS . No short text exist

W I S . No s!lOrilexie XI . No shorttekieHs

W "

:/ p g zz:: ZBV . No short lext exis

'i D g O1; 2 IDES ;.EL. 828-IDES Notice t h a t , the Sendor, Receiver

r y ~ . ~,,s~;~,;~;~:,;,:;p~<;, i DE3-K48A

DH~- ID^ and Message Type Details Are

i> gr<,:aac~,~?.,:j _._._-._._._-_._._-._._-_-_--.< ~ ~ : C ~ ; , ~ ; ~ . I ; : ~ ~ ~ _._{... .}_{.. .}_._..._._._.-_._._..c:];~:,! _._._-_._._-._._-_-_._-._._-_._._._._._._.EBP-TO-R3

:. - -. . . -. . - - . ... ADDed -

.I

" %.~~?!!!~!!~~."!.C:!.P~!~?"!I~!!!~??.~...~..~~.IE;!E!~.~!L~

r @ e 0 0 ~ 1 i n e i 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.

eMax Technologies,Ameerpet,Hyderabad

(38)

(39)

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

(40)

5. Distributing the Master Data Via Standard IDocs

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.

INBOUND Configuration Settinpts:

" < 'I'

2

MAINTAIN INBOUBD Partner profile (WE20) :

(41)

We Never Co~npromise In Quality. Would You?

SAVE IT.

SELECT THE Partner SENDOR AND CLI BOUND

PARAMETERS

ID.

/

Page 9 of 39 By Ganapati Adimplam

(42)

5. Distributing the Master Data

Via

Standard IDocs

We Never Colnpromise 111 Quality. Would You?

NOTE

:

BOTH OUTBOUND AND INBOUND CONFIGURATION

SETTINGS ARE COMPLETED.

WE

CAN TEST THE COMPLETE

PROCESS OF SENDING THE COST CENTER AND RECEIVE IT

AND POST(CREAT) THE SAME IN THE RECEIVER SYSTEM.

(43)

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 2 0

-' 4-& 4

Enter the Controlling Area 1000(Standard)

,

Cost Center - 3500

,

Message type

-

COSMAS and Target System as RECEIVER and EXECUTE IT

ENTER

Page 11 of 39 By Ganapati Adimulam

cMax Technologies,Ameerpet,Hyderabad

(44)

5. Distributing the Master Data Via Standard IDocs

We Never Co~nproinise In Quality. Would You?

ENTER.

4

EXECUTE WE02 / WE05 TO CHECK THE IDOC NO AND DATA RECORDS

AND STATUS OF IDOC.

lo 24:OO.OO 0 0 . 0 0 DOE, 4 ; 0 6 02 2008 LO 06 02 2008 - e ; 0 0 . 0 0 0 0 10 2 4 . 0 0 - 0 0 -, te o f ~ a s l Change 10 4

--

+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.

--"

- -

"

@ f V * * " -" - a + n r A @a@ ;E~,$>> &%A 2 C SAP

Page 12 of39 By Ganapati Adimulam

4 _{eMax Technologies,Ameerpet,Hyderabad}

Ph No :+9140 -65976727, Cell NO : 9948444808,98490 34399, wmv.emaxtech.corn

(45)

5. Distributing the Master Data

Via

Standard

IDocs

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

L '%

SUCCESSFULLY. ap?t **.

(46)

5. Distributing the Master Data Via Standard IDocs

We Never Cornpromise In Quality. Would You? 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

(47)

We Never Colnprornise I11 Quality. Would You?

2) Get/Fetch/Yull

Whole

Copy

SENDOR Request RECEIVER

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 ~ y p e Outbound

%>. X *.

Type .?, &:*.; I ' Program1 Program1

4 Customers ALEREQOl BD13 DEBF Materials Fetch Materials Send Vendors COSMAS01,02,.

.

BD16 COSM

1

Customers Send Vendors Fetch MATFET

I

Centers

J

CREMAS CREFET Centers Fetch Cost

Page 15 of 3 9 By Ganapati Adimulam

eMax Technologies,Ameerpet,Hyderabad Ph No :+9140 -65976727, Cell No : 99484 44808,98490 34399, w~~~.emaxtech.com ALEREQOl 'DEBMAS 1 DEBMAS01,02,.

.

CREMAS01,02,

...

ALEREQOl COSFET B D l l MATF BD12 BD14 BD15 ALEREQOl DEBM CREl CREF BD17 COSF

(48)

5. Distributing the Master Data Via Standard IDocs

We Never Coinpromise In Quality. Would You?

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

% s w

SENDOR TO RECEIVER AND THE SAME

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)

eMax Technologies,Arneerpet,Hyderabad 3

(49)

We Never Cornpromise In Quality. Would You?

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

pi

EXECUTE BD64 AND Click On Change -

4

li lulodel views I

P L N O shorttern exlsts BBP-DII NO snort text exists BC61 9-300 N o s h n r t t r x * exists BELCO NO short text eXlstS BlT300-BP N o Shorttext exists CONS0LIDC.T N u s h o r t t e x t exlsts D I Z - I D 3 N o short text exlsts

DlZ-IDBCLN N o shot? text exlsts EBP3DO-R3 NO shorttext e x ~ s t s HR-ORG-SEM NO s h o r t t e l d exlsts . N o s h o r t text exists text exists . . 4 * -

" @ 'S

8"

Fllter model ollsplay

/

- Create model view

1

2 lirid BAPI - A * kcd t-n~?-;sage ".-" 4pe A

+..ni

.

;. i r - 's%w" ,urn,.-- ,, *uc, .Ps- ;? -m-,n 7 .

_-__i___ --I__----__-

-

7

~

--

/

01sttil)ut1oti Mudel ' 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

(50)

5. Distributing the Master Data Via Standard IDocs

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 :

10

Add message iype i

Select the Distribution Model andclick O n Add Message Type - , .

, No short text exists

b

z

r J ~ - - ~ ~ ~ ~ P-DII . No sliort text exists

p

zi

a;:,?; ;3-:;;3 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 ₄ 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

z

-<:yi$i 21 5 . No short t e d exists

D gji,~;~-:;js RCUS . No short text exists

p

zz

: ~ ~ ~ - ~ [ . , i j ' ~ q B-BUYER . No short text exists

['/ >SH-SI,J"$.;:' B-SUPPLY. N O short tm< exists

p.

4 g

2;s

D ~ s j e s s j ~i::;: 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

,q

;,

q *:-, : r) 7 r ,

b

#

S,.,

...

..,. .;i i .. c.5 4.53

D SF:!.. $;h:,?,e:: -Ei;Jzlp;o

C, 3H3..:.,:3:$ i 1,f;'J ,<..? ;ij:$

PROVIDE SENDOR, RECEIVER AND MESSAGE TYPE To be Transferred.

(51)

We Never Compromise I11 Quality. Would You?

ENTER AND SAVE it.

(52)

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: I n the Outbound Partner Profile, We Maintain the Below Information.

Whom to Send What to Send Medium Of Data Mode Of Dispatch

Tranlffer

Partner (RECEIVE R) Message Type + IDoc Type

Note : We always Create Only file for each receiving(Par and One

Entry for each Message type we r .

(53)

We Never Coinpro~nise In 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.

, .

. \

(54)

5. Distributing the Master Data Via Standard IDocs

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

(55)

We Never Compro~nise In 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

(56)

5. Distributing the Master Data Via Standard IDocs

We Never Com~romise In 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

(57)

We Never Co~nprolnise I11 Quality. Would You?

ENTER MESSAGE TYPE ODE(C0SF) AND

TriggerImmedia tely.

I

NOTE

:

BOTH OUTBOUND AND INBOUND CONFIGURATION

SETTINGS ARE COMPLETED. WE CAN TEST THE COMPLETE

PROCESS OF REQUESTING THE COST CENTER AND

RECEIVE IT AND POST(CREATE) THE SAME IN THE

REQUESTING SYSTEM.

eMax Technologies,Arneerpet,Hyderabad

(58)

5. Distributing the Master Data Via Standard IDocs

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

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

(59)

Master Data

. . . . . . , ?---..--

-

Cost Center 7 8 6 E U.AX TRAII'.III.IGS Controlling Area I Cl0U CO Europe

Valid Ftorn 11 . 3 2 2003 to 31 . I ? . 9959

. ... .

Basicdata

\

Contt.01 3 T e i i ~ p l a t e s Address Commui~ication

i:

Histoty , ; *

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

.---"

Efr~lWTRAININGS Description SAWTRAINING DIVISION

--- " " ---- - - " . - - -"--a ---- " " Basic data , /

'

[ % o ~ ~ ~ s p o n s i b l e tulr.Rarna Rao

1

Department

1

a I

j Cost Center Cateyor>{ E Development

H - AC41 0 _{Traininy AC410}

/

Hierarchyarea

! Company Code 1 0 0 0 IDES AG

/

Business Area 9 9 0 0 Corporate Other

1

Functional Area

8

"

Currency EUR

Profit Center

(60)

5. Distributing the Master Data Via Standard IDocs

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 a t 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

(61)

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

(62)

5. Distributing the Master Data Via Standard IDocs

We Never Compromise 111 Quality. Would You?

$

r^--.---.---.---.---.---.7.---.---...---F..

@

_2.

,st,,,,_._._._._.. . . ID,,, . . . created . - - - - . - - - . - fur - - -

-

- - - - - - .,I?ssa,e . * . - - -

,,,

. . . - -

,,,,As;

- - .

-

. - - - - - .

i

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-@ C e ~ & @ @ - z fm#Z8a# S~reen

Master Data

Page 30 of 39 By Ganapati Adimplam

eMax Technologies,Ameer~et,Hyderabad

(63)

"-"-" ---"-"--

-

---- "-" --*-

-7

Etl~1.4X TRAININGS

1

I

1

Description SWd TRAI NI Id G DI'JIS ION

,--- - ₇_-_-_-_-_-_-_-_-_-_-

-Business Area Corporate Other

Y

V

eMax Technologies,Arneerpet,Hyderabad

(64)

5.

Distributing the Master Data Via Standard IDocs

We Never Coln~rolnise In 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) a t 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

Paltner no. SENDOR Patrierno. REGElYER

RECEIVER , Direction - 0 1 (Outbound).

,

SENDOR, Direction - 02(INbound).

3)SEND COSMAS (Cost Center) EXECUTE WE02 For COSMAS at

4) Post COSMAS (Cost Center) Execute WE02 For COSMAS at

RECEIVER(8 1 O),Direction02(INbound).

I

(65)

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

(66)

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 : ~ ~ ~ ~ --- - ~ * L ~*--? ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ . ~ ~ . ~ ~

ip

Change pointers activated - generally

/

1 ..._...----,-....---,---m--- i

I

t

Select the Checkbox and SAVE it. ₄

(67)

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.

(68)

5. Distributing the Master Data Via Standard IDocs

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

(69)

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

:

oram EXECUTE RBDMIDOC Pro,

CASE 1 : Execute for the ~ i r s t time

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

(70)

5. Distributing the Master Data Via Standard IDocs

EXECUTE RBDNIIDOC Program

c # " @ a g j g a ! g #fD@G Ty#3@ f ~ a r f 8 C F # B # B $ ~ P o ~ # ~ ~ @ T s

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 P S e r e e r a

Master Data

C n s t Center PEE

t?

5

(71)

-

_{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 E Development C o s t Center C a t e p o w 1 Hierarchy a r e a H - P . C 4 1 0 Training A C 4 1 0 ! 1 C o m p a n y C o d e 1 0 0 0 IDES A G B u s i n e s s Area 9 9 0 0 Corporate Other Functiortal A r e a

E U R

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.

(72)

(73)

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.

(74)

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

(75)

We Never Com~romise in Oualitv. Would You ?

DEBMAS -> Message type For Customer Master.

I

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

(76)

6.Piltering

? . - .

y ; ~ J l ' , . ' l S l O n

IG.1 E;.sles Organization

-

I., . : Cli.;trihution Channel

Dlvislon

:

,d Sales ~ r g

Dlstr~butlo&%

Click I..: ;:.3L1;-t Rows and Enter Value Company Code GL1000(1000)

. . Pag: -, ,,. -A By Ganapati Adimulam eNlax Technologies,Ameerpet,Hyderabad :.: P:,) :+91 40 -65976727, Cell No : 99484 44808,98490 34399, ~7nv.emaxtech.com

(77)

We Never Com~romise in Quality. Would You ?

SAVE it.

(78)

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

(79)

We Never Com~romise in Oualitv. Would You ?

SAVE it.

Testing

:

Create a Customer in Company Code 3000.

Execute

XDOl

to Creating Customer.

(80)

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

(81)

We Never Comvromise in Oualitv. Would You ?

ENTER

$ ,\ \A,

Check

for

the

IDOc

: - 4". - \, , , !W

Executer WE05 \ \

,.I"w

---"

""* - " "

-"

-

-, ,

-

,. ,, , ,

-

,,,~~ -,, .,, ,,,, *- ,,,,,," ,,, , ,,, , - ,. , "