MIRO outbound IDOC ALE settings

Hi Friends
PLz tell Output Type, Process Code etc...for MIRO outbound.
for inbound i am using INVOIC01..
Thanks and regards

Hi Madan,
The process code is SD09. Check we64 for more info.
Regards,
Ravi

Similar Messages

ALE settings for MIRO outbound IDOC

PLz tell Output Type, Process Code etc...for MIRO outbound.
for inbound i am using INVOIC01..
Thanks and regards

Hi madan,
u can use the transaction NACE to find out the output type of MIRO.
If u know the function module u can able to find the process code easily.
Since function module names are based on message types.
Regards...
Arun.

Any training course on IDoc/ALE

Hi Friends,
I am working in SAP SD area. For the day to day tasks I need to work on Interfaces. If there is any error arises then, I have to look whether there is any problem from application (SD) side. If it is related to XI team, they will fix it.
I would like to know more about IDocs, ALE settings such as Partner profiles, Message types to name few. Is there any training course that deals with IDocs/ALE from basics to little advance for a functional or application guy like me? (I mean not getting into too technical)
Could any one name the course title or the number. I can take the class room training (in English language) anywhere in Germany/Swiss/Austria/Belgium/Findland/Denmark/Norway/Netherlands/Italy.
Thanks in advance & Br,
Sats.

Hi Friends,
I found one course called BIT300 for ALE.
Is this course also designed for an Application (Functional) consultant? or is it too technical?
Could anyone please let me know.
Thanks & Regards,
Sats.

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

ALE Settings for IDOC Processing

Hi,
Can anybody tell me what all the ALE settings I have to look for any IDOC.
Thanks,
bsv.

Hi,
Please check this link for ALE setup for inbound and outbound processes.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Regards,
Ferry Lianto

ALE Settings error: Outbound: LS to KU

Hi Guys,
Requirement: send idoc to customer 1000358 (KU) when user execute a report in R/3
when user execute report we have written the code for idoc generation using function module
MASTER_IDOC_DISTRIBUTE. the idoc number is geeting genarated successfully with sy-subrc 0
although its giving an error in WE02 that:
IDoc: 0000000003560240 Status 29: Error in ALE service
Could not determine recipients for message type ZNACPRLST
its not picking the recepient information of the customer from ALE settings.
I have added that recepient info forcefully in debug before function module MASTER_IDOC_DISTRIBUTE.
But again the idoc number is geeting genarated successfully although its giving
another error in we02 that:
IDoc: 0000000003560258 Status 37: IDoc added incorrectly
Entry in outbound table EDP13 not found. please check the partner profile.
Although i have checked tht the entry exist in above table in se11.
ALE Settings:OUTBOUND:
Sender: LS- SP5CLNT210
Receiver: KU - 1000358
idoc type: ZPRLST01
message type:ZNACPRLST
WE82 assign idoc type with message type.
Receiver port: SAPOUT (File type & Transfer idoc immediately, RFC destination also there)
Partner profile: partner no: 1000358
                  partner type: KU
                  outbound params: message type - ZNACPRLST
                  But nothing i did in message control for outbound process code becoz we are
                  generating the idoc in the report itself by coding.
Distribution model: i can not create any distribution model. Because recipient system is KU.
                    and therefore no logical system name of recepient. therefore system will
                    not allow to create distribution model unless we have a logical sys name
                    of recipient. And i think as the recipient sys is KU (not LS) therefore
                    no need of distribution model?
I dont have any configuration for inbound till now. And i believe that doesnt matter
for outbound trigger.
Please can anybody tell me what could be the error in ALE settings that sytem is showing?
Will appriciate any help....
Thanks,
Biswajit.

Hi,
thanks for your reply.....
i did exactly in WE20 that i wrote before...
The file port for EDI system is also perfect otherwise it woudnt work for other standard idocs...right?
i m tried to retest the same in We19 as well....
but it is giving the same below error:
IDoc: 0000000003560240 Status 29: Error in ALE service
Could not determine recipients for message type ZNACPRLST
its not picking the recepient information of the customer from ALE settings.
If I added that recepient info forcefully in iwe19 and retest it again the idoc number is geeting genarated successfully although its giving another error in we02 that:
IDoc: 0000000003560258 Status 37: IDoc added incorrectly
Entry in outbound table EDP13 not found. please check the partner profile.
Although i have checked tht the entry exist in above table in se11.
Your comments pls...
Thanks,
Biswajit.

Outbound IDOC for MIRO transaction

Hi Experts,
What would be steps innolved in trigerring an (outbound ) IDOC when an inovice is posted using MIRO transaction.
How can I send the idoc automatically in the outbound ALE layer. Is theres any message type to set up or any program to be execute.
Basically certain information in the Invoice has to be captured in the IDOC.
Regards

Hi Raghvendra,
I my scenario, i will be creating the inovice in SAP manually using t.code MIRO and once the invoice is posted i need to capture the details in IDOC. The EDI customization would come into picture for receiving invoices through EDI.
Regards

Need of ALE settings to connect 4.7 to 5.0 to send IDOc

Hi
I have two servers 4.7 and 5.0 .
Now I want to send Idoc from 4.7 client 800 to 5.0 client 800.
Can anybody provide me the steps to create ALE settings and to send IDOC.
creating logical systems in source and destination and creating RFC and partner profile and port.
Thanks in Advance

Hi,
For ALE senerion for sending the material from one system there are three methods are there
1) Executable program only for Master Data
2) Message type Master As well as Transcation Data
2) Change Pointers Master As well as Transcation Data
1) SCC4 Create the Logical systems.
ALG800 for 800
ALG810 for 810
2) Assign the Logical systems to the Client using SCC4> selecting the Client and Double click> maintain the logical system name which you had created in the step 1
3) Main RFC destination SM59---> use the same Logical system name as the Logical system name
log on to 800 and goto SM59 --> create
ALG810 --> provide the 810 logon details and save
test with remote logon...it will open the client 810..
logon to client 810 goto--> sm59 --> create
   ALG800 --> provide the 800 logon details and save
test with remote logon...it will open the client 800..
logon to 800 goto BD64 maintain CDM-->change
create CDM
ZCDM01 CDM
ALG800 sender
ALG810 Reciever
MATMAS Message type
ZCDM01 CDM
ALG810 sender
ALG800 Reciever
MATMAS Message type
save
Environment ---> Generate partner porfile.
edit --> distribute CDM
Logon to 810
goto BD64---> select CDM ZCDM01 ---> Environment ---> Generate Pratner Profile.
Edit --> distribute.
ALE Setting are compleated.
Logon to sender system 800.
create material in MM01
Material   10001
Industry sector mechanical engee
Material Type finished
enter
Base Unit of Measure KG
Weight unit         KG
Gross Weight         100
Net Weight           100
save
Execute BD10 in client 800
Check the Idoc in WE05.
Log on to Client 810
Execute BD11
check the IDOC status in WE05
goto MM03 provide the material numer enter...
Thansk,
Nelson

Idocs are not prosessing even after ALE settings in SAP XI and ECC

Hi Experts!,
<b>I have a system which has SAP ECC and SAP XI 3.0 installed with 2 instances on the same operating system. ( In MMC you can see ECC and XI under the same SAP console tree ).
I have made many times all possible ALE settings between ECC and XI and I was unable to deliver the IDOC [ Idoc scenario- unable to get the IDOC in the receiver side (R3)]
Could any one please let me know how to solve this issue.
Useful answers will be rewarded.
</b>
Thanks in advance!,
Sunil

Hi Martens,
I appreciate your kind reply, error : Unable to convert ALE logical system.., this is the error message I am getting, while I do File to IDOC scenario. So what may be the wrong thing in this configuration, Have done ALE settings ( Log sys, assign log sys, partner profile, port and RFC connection from R3 to XI).
So could you please let me know the solution.
regards,
Sunil

Ale settings or idoc issue

Hi
Am able to send idoc successfully from ecc 6.0 but i can see them in target system dont know where am mistaking in Ale settings or where pls help me out its bit urgent requirment.
Regards
Meeta

Hi,
did u check what i suggested.....sender side it seems fine..but u hava also set settings in reciver side also..Please check the below things
1>WE20(Partner profile) in reciver side..
here u will specify the partner as sender partner,and in the inbound paramters u have to give the messagetype and process code...see if u have done these settings in inbound side....
Regards,
Nagaraj

ALE Settings For File-IDOC Scenario

Hi All,
While Doing IDOC-File Scenario we have to do the Following Settings
In XI
1) Create RFC Destination towards R/3
2) Create Port
3) Load Meta data
In R/3
1) Create RFC Destination towards XI
2) Create Port
3) Create PF
Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
Clarify me these Confusions
Regards
Bopanna

HI,
for IDOC TO FILE
We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
i.e for FILE-IDOC
1) No need to Distribute the modal view
2) For partner profile Specify the INBOUND PARAMETERS
FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
We need to do the following settings in XI
1)   Create an RFC Destination to the Receiving System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select Create New button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in XI towards R/3
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Inbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Message Type and Process Code.
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
PLZ REFER THE LINK BELOW.
PLZ REWARDS THE POINTS
VIKAS JAIN
                                                                                [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
Edited by: vikas jain on Jan 22, 2008 11:49 AM

Outbound IDOC for MIRO

hi
My requirement is to send the incoming vendor invoices detail to an external system. Are there any IDOCs that i could use for this purpose??
Regards
Sujai

Hi
Check the below thread
Re: Outbound idoc for MIRO
Regards
Pavan

ALE Settings for IDOC

Hi,
For configuration of IDOC adapter
1) we need to create RFC Desination both XI System and R3 System.For port creation if v given same port name in both XI system and R3 system it will work or not ?
2) On Receiver SAP system, we need to configure the logical system normally for XI system, were v can find logical system of XI System.
3) Can RFC Destination b same on both systems( R3 system, XI System)
Regards,
Praveen

Hi
The following configurations are needed for Idoc scenarios
1) ECC Configuration : a) Create RFC connections from ECC to XI in SM59. rfc connection name should be target XI logical system name . BD54 or SALE are the tcodes for checking the logical system for respective client.
                                   b) Create port in we21 & provide the above RFC destination.
                                   c) Now Create Partner Profile in we20 ...partner profile name should be target logical system name.
                                        assign the outbound parameters with receiver port created in we21.
2) XI Configuration : a) Create a RFC connection for XI to ECC ...rfc name should be target logical system name(ecc).
                                  b) Create port in IDX1...it should be SAPXXX..where XXX is the ecc system id.
                                  c) Import the idoc metadata in IDX2.
For Outbound idocs generate the model view in BD64.
Regards
Abhijit

ALE IDOC : Probelm in outbound idocs.

Hi,
I am sending an outbound idoc from system A to System B. In we02 i see the idocs are generated successfully with *Status 03 Data passed to port OK.
*With message "The IDoc was sent to an SAP system or an external program via a transactional RFC."
"The TID is xxxxxxxxxxxxxxxxxxxxxxxx'.
But the Idocs have not reached Sytem B.
I checked SM58. Here I see the for TID xxxxxxxxxxxxxxxxx
the below message
"ALEREMOTE | IDOC_INBOUND_ASYNCHRONOUS | SYSTEMB 'No authorization to send IDocs with message type'
*I have send the same IDOC from SYSTEM C (Sandbox) to SYTEM B. *This works and the user profile is same in SYSTEM C and *SYSTEM A.
I am not able to trace the probelm. Can somebody help here.
Also if anybody can help me understand what happens when a outbound idoc is susccessfully processed with status 03.
Is there a program that processes the idoc after status 03 using TID no.
Please help

hi martin,
when i send it from system c (sandbox) with same user the idocs are not in error. but when i try to post the same from system A with same user with same profile(already checked with basis) the error occurs.
can give some hints what could be the reason.

ALE settings in xi

1) what are the ALE settings i have to maintain in R/3 system and XI in Idoc 2 file scenario?(I know little bit RFC Destination, Port, Partner profile in R/3 system. is it required to maintain the port in XI also? )
2) what is use of Meta data ( IDX2 )? can we import it every time explicitly ?
3) what are the ALE settings i have to maintain in R/3 system and XI in File 2 Idoc scenario?
4) should i create ports in both R/3 and XI systems?( idoc 2 file / file 2 idoc)

Hey,
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
reward points if useful.
regards,
       Milan

MIRO outbound IDOC ALE settings

Similar Messages

Maybe you are looking for