Answer / guest

Hope the below procedure will work it includes with message
control and with out message control



Create IDoc type (WE30) Client independent

The IDoc type refers to the IDoc structure that you will
require for your development. . This IDoc type will have 1
segment . If you require many segments or nested segments
then they are also created using the same procedure.





To create the IDoc type, follow these next few steps:

• Enter transaction WE30 (ALE -> Extensions -> IDoc types -
> Maintain IDoc type)

•

• Click on Create new (we are creating an IDoc from scratch
but you may want to copy another IDoc if it is similar to
your requirements) and enter a description, and press enter

• Enter the segment type (must start with Z1), check
mandatory if the segment must exist (in this case check
it), enter 1 in minimum number and 1 as maximum number.
(Make the maximum number 9999999999 if there are going to
be many of these segments in each IDoc. IE. When line items
are passed via IDocs), click on Segment editor

• Enter a description for your segment type and create

• Enter a description for your segment, enter each field
required in your IDoc,

• Save and generate, press back

• To release the segment choose Goto, Release from the menu

• Check the box on the line of your new segment

• Save, back and enter

• Your IDoc type structure should be displayed with your
new segment

• Save and back

• To release the IDoc type choose Extras, Release type from
the menu and Yes

Your IDoc is now ready for use. If you need to add fields
or segments to your IDoc type, you will need to cancel the
release of the IDoc type as well as the segment release
using a similar

procedure followed above (except now you uncheck the
release box for the segment and you choose cancel release
for the IDoc type).

Create message type (WE81) Client independent

To create a new message type, follow these next few steps:

• Enter transaction WE81 (ALE -> Extensions -> IDoc types -
> Maintain message type for intermed. Structure -> Create
logical message type)

• Choose Create logical message type by double clicking on
it

• Click on change icon to enter change mode

• Click on New entries to add a new type
• Save and exit.

Your message type has now been created. The next step will
be to link it to the IDoc.

Link message to IDoc type (WE82 & BD69) Client independent

To link the message type to the IDoc type follow these next
few steps:

• Enter transaction WE82 (ALE -> Extensions -> IDoc types -
> Maintain message type for intermed. Structure -> EDI:
Message Types and Assignment to IDoc Types)

• Click on change icon to enter change mode

• Click on New entries to create the link

• Enter transaction BD69 (ALE -> Extensions -> IDoc types -
> Maintain message type for intermed. Structure -> Assign
message type to IDoc for ALE)

• Click on change icon to enter change mode

• Click on New entries to create the link


• Save and exit

Your IDoc is now linked to your message type. We still need
to link object types and add the message to the model
before we can use the message.

Maintain object type for message type (BD59) Client
independent

The ALE objects are used to create links between IDocs and
applications objects, to control the serialisation, to
filter messages in the customer model and to use listings.

For our own message type and IDoc you must maintain object
types for the links.

If you want to check the serialisation for the message
type, then you must maintain object types for the
serialisation. If no serialisation object has been
maintained for a given message type, then the serialisation
will not be checked for this message type.

To add an object type to our message type, follow these
next few steps:

• Enter transaction BD59 (ALE -> Extensions -> ALE object
maintenance -> Maintain object types)

• Click on New entries

• Save and exit.

You have now created an object that we’ll use as a filter
object in the customer model to direct the flow of messages

We now need to add our new message type to the distribution
model.

Configuring the Distribution Model

This task is performed on your ALE reference client.

Manual Configuration (BD64) Client dependent

OUTBOUND PROCESSING
To manually configure the customer distribution model, read
the ALE configuration procedure, and follow these steps:

• Perform the Maintain customer distribution model directly
function. (ALE -> Distribution customer model -> Maintain
customer distribution model directly)

• Specify the customer model you want to maintain and the
logical system that is to be the sender of the messages OR
create a new model.
• Choose the receiving systems to which the sending system
must forward message type .

• For each receiving logical system allocate the message
type necessary for communication to the receiving systems
as per ALE configuration procedure.

• Create filter objects
• Save the entries.

To change the owner of a model, choose the 'Maintain
ownership of customer distribution model' function. Make
sure that all changes will be distributed to all systems
that know the corresponding model. To do so, you can use
the correction and transport system.

To transport the customer distribution model you should use
the Distribute customer model function of the IMG as
described below.

Distribute customer model (BD71) Client dependent

After the customer model has been created centrally, it
must be distributed to the other remote systems. This
entails first of all setting up the communication for the
distributed systems and then sending the model.

Distribute Model (BD71) Client dependent

This task is performed on your ALE reference client. To
distribute the customer distribution model, read the ALE
configuration procedure and follow these steps:

• Make the settings for the communication with the other
decentral systems, you have not set them yet.

• Define the RFC destination for R/3 connections whose
names correspond to the name of the corresponding logical
system.

• Create the output partner profile.
● Out bound process code- if you are using outbound
processing under Message Control, the IDoc is generated in
the IDoc Interface. The process code names the relevant
function module.
while creating partner give the appliocation as for sales
and message type and process code created as per the
requirement .

• Distribute the customer model

• Specify the name of the customer model.

• You must specify the target system to which you want to
distribute the customer model.


Maintain sending system partner profile (WE20) Client
dependent

With this function, you define the partner profiles for all
outbound and inbound messages on the basis of the customer
distribution model.

After you have defined and distributed the customer model,
you will have to maintain the partner profiles locally.

• Enter the output mode (background, immediately) and the
package size for outbound processing.

Requirements

• The customer model must be maintained.

• RFC destinations must be maintained.

• The customer model must be distributed.


. INBOUND PROCESSING

For creating inbound partner

● Inbound process code- names the function module or
workflow which reads the IDoc data and transfers the data
to the application document.

Maintain ALE attributes

The inbound function module needs to be linked to the
message type and the message type needs to be linked to the
appropriate inbound process code at the partner profile
level before the scenario is enabled. These steps are
described below in detail.

Link Message Type to Function Module (WE57) Client
independent



• Enter transaction WE57 (ALE -> Extensions -> Inbound ->
Allocate function module to logical message)

• Enter and save

Define FM settings (BD51) Client independent

• Enter transaction BD51 (ALE -> Extensions -> Inbound ->
Define settings for input modules)

• Click on New entries

• Save and Exit

Maintain process codes (WE42) Client dependent

A process code needs to be maintained on each client. It
then needs to be linked to the message via the partner
profiles on each client. This allows the various clients to
use a unique function module for the same message type.

To maintain the process code follow these steps:

• Log on to the appropriate receiving system client

• Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining
process codes inbound)

• Choose Inbound with ALE service

• Choose Processing with function module

• Click on Processing with function module and choose
create icon

• Click on New Entries

Create inbound partner profile

For each message type you need to maintain the inbound
partner profiles.

Maintain receiving system partner profile (WE20) Client
dependent

• Enter the output mode (background, immediately) for
inbound processing and NO message code.

Regards,
Subhani.

What is valley, Playa, Catchment area, Basin ? please describe with picture.

0 Answers  

---

without administrator right how to run iis services

0 Answers   V Angelz Technologies, Wonder Products,

---

what an interviewer wants to see in the candidate.

0 Answers  

---

I forgot my E-mail ID Password. So, anyone send me the date for clerical interview for SBI.My Email id is dhanssmailbox@gmail.com

0 Answers  

---

hi, i have been selected for sbi po(rural business).But due my fault,I could'nt take application print out.Now they are demanding to submit it at interview. What to do? Pls help if anyone can......

0 Answers  

---

---

tell me some thing about yourself?

0 Answers  

---

what is the distance between sabarmati ashram and dandi

2 Answers  

---

what do you know about this company ?

0 Answers  

---

Tell me about your school

0 Answers   HGS,

---

Which country in the world has 13 months? Hint: Its an African Country. It has exactly 30 days per month.

2 Answers  

---

Whether exchange 2000 have Recovery storage group

0 Answers   Cognizant,

---

plz tel me what r the questions asked in bank clerikal posts

0 Answers  

---