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.

i am selected for sbi bank po as well assistant central intelligence officer grade 2 executive in intelligence bureau. which one i should join and why?

2 Answers  

---

How are You? Punchline of Which Co.

1 Answers  

---

What is the probability(i.e. chances) of collision of two people if initially both are moving in the same line but always they used to turn opposite to each other(if one is taking right turn means another is taking left turn and vice versa)?

1 Answers  

---

Hi,i m facing to many problems at interviews,that is i got 10th and 12th was 3rd classes,and my degree in one year gap with 2nd class,and my mca in 65%,i m going to any sw companies my resume rejected,what can i do?

0 Answers  

---

who won the padma shri awrd recently?

1 Answers  

---

---

Can any one solve this one?? **A server configuration is controlled from a single web page with multiple options:  20 drop-down menus, with 3-4 options each.  5 check-boxes.  1 multi-select menu, with 5 options.  1 template selection, with 6 options: A, B, C, D, E, F. o When options A, B, C, D are selected, all options (#1-#3) above are available. o When options E, F are selected, only 10 out of 20 drop-down menus have an effect.  Besides item #4, developers input is that all options are independent, I.e., not impacting each other. What is the required number of test configurations required in order to test the server configuration and release in good quality:  Assuming first release.  Assuming regression tests for release with new features not impacted by the above options. Test configuration is a complete set of options that were selected to be tested in one complete server configuration scenario. I.e, a test configuration is set of 17 or 27 specific options tested together.

0 Answers   Navionics,

---

when will we get the appointment letter for the SBI clerk Post? Since I selected in the final list of recruitment 2009..

0 Answers  

---

How to answer for a question in a company interview that what are three positive character traits you don't have?

0 Answers  

---

can any one tell me about character certificate. I am confused because according to information voucher we will have to bring 2 character certificate & I have only 1. so please tell me how can i get the other one.

0 Answers  

---

Which FI Accounting entry is being posted after PGI?

0 Answers   Baidu,

---

different of bank statment and stock transfer in cash book

0 Answers  

---

Women want liberation. What kind of liberation? From Whom or From What?

0 Answers  

---