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.

Similar Messages

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

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

ALE settings for IDOC2FILE Scenario

Hi All,
I have the requirement to work on IDOC2FILE scenario. i am not able to do the ALE settings well in both R/3 side and XI side. Anybody have the full documentation with step-by-step analysis, please send me ASAP. Please help me in this regarding.
I am very thankful to you all in advance.
Regards,
Nag.

Hi Nagarjuna kumar ,
The following websites give u step-by-step solution for ALE settings for IDOC2FILE Scenario:
A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
cheers!
gyanaraj
****Pls reward points if u find this helpful

How configure a Logical System (XI) as receiver for an Outbound Idoc?

Hi all,
How can I configure a Logical System (XI) as receiver for an Outbound Idoc?
Points will be given,
Regards,
Daniela

hi,
it all depends on what kind of document you need to send to XI
if you want to send some logistic documents (like orders, deliveries etc)
have a look at my book - where you will find step by step guides
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
then you will undestand where to change to get it send via LS
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Standard program for creating outbound IDoc holding wbs+cost plan

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

Standard program for creating outbound IDoc including wbs + cost planning

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

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

Steps for configuring Outbound Idoc OILSHI01

Hi experts,
 can anybody tell me the steps how to configure an Outbound IDOC.
 It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
 if not anything else will also do.
 Kindly give me steps in detailed. Since i have never done this. Including
 distribution modle (BD64). in which case it generates the Automatic Partner
 profiles.?
<REMOVED BY MODERATOR>
Regards,
Umesh
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

Hi Umesh,
Sorry for the late reply. Let me clear your couple of misconceptions first.
Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
Now the further steps:
Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc.
Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
 a. trigger the idoc on saving the doucment. this triggers idoc as soon as you save the idoc.
 b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
 c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
Hope this was helpful.
<REMOVED BY MODERATOR>
Cheers,
Karan
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

BADI for PO OUTBOUND IDOC

Hello Experts,
Please help me out finding a suitable BADI for T code: ME21N
OUTBOUND IDOC.
Scenario:
I have to populate a "Z" segment while creating an IDOC in ME21N. for this I require a BADI.
I have tried using FM: idoc_output_orders
Form Routine fuellen_idoc_inttab.
but ME21N doesn't execute it at all !!!
I have set my Output Type to EDI with the Valid Settings
when ever i create a PO it creates an IDOC but it doesn't execute FM idoc_output_orders
Thanks in Advance!!!
R

Hi,
Below steps for your reference.
1.M/59 Define Condition Tables
2.M/50 Define Access Sequences
3.NACT Define Message Types
4.Set up fine-tuned control for each message type
5. NACZ Define Message determination shemas
6.NACR Define Condition Records
Regards.
David.

Recommended Status Codes usage for Inbound & Outbound IDocs

Hi,
Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
I assume we use 51 for Posting Program (not 56) and
26 for a Z-Selection Program (Not 37 or any other Code).
Please let me know what is recommended and which status codes most of the people use while Custom Development.
Thanks and Regards,
Venkat.

Hi,
Outbound IDOC Status Codes
The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
Outbound IDOCs
Code Error Event Severity SAP Meaning
02 Yes Error Error passing data to port
03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
04 Yes Error Control information of EDI subsystem
05 Yes Error Translation
06 No Harmless Translation
07 Yes Error Syntax check
08 No Harmless Syntax check
09 Yes Error Interchange handling
10 No Harmless Interchange handling
11 Yes Error Dispatch
12, 13, 14 No Harmless OK
15 Yes Warning Interchange acknowledgement negative
16 No Harmless Functional acknowledgement
17 Yes Warning Functional acknowledgement negative
18 No Harmless Triggering EDI subsystem
20 Yes Error Triggering EDI subsystem
22 No Harmless Dispatch OK, acknowledgement still due
23 Yes Error Retransmission
24 No Harmless Control information of EDI subsystem
25 Yes Warning Processing despite syntax error
26 Yes Error Syntax check
27 Yes Error ALE error
29 Yes Error Error in ALE services
30 No Harmless Ready for dispatch (ALE)
31 No Harmless IDOC is marked for deletion
33 No Harmless Original of an IDOC which was edited
34 Yes Error Error in control record of IDOC
36 Yes Error Timeout error; electronic signature not performed
37 Yes Error IDOC added incorrectly
38 No Harmless IDOC archived
39 No Harmless Receive confirmed
40 Yes Error Application document not created in target system
41 No Harmless Application document created in target document
Inbound IDOC Status Codes
The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
Inbound IDOCs
Code Error Event Severity SAP Meaning
51, 52 Yes Error Posting error
53 No Harmless Posting successful
54 Yes Error Error during formal application check
55 No Harmless Formal application check
56 Yes Error IDOC with error added
60 Yes Error Syntax error
61 Yes Warning Processing despite syntax error
62 No Harmless IDOC passed to application
63 Yes Error Error passing IDOC to application
64 No Harmless IDOC ready to be passed to application
65 Yes Error ALE error
68 No Harmless IDOC is marked for deletion
70 No Harmless Original of an IDOC which was edited
73 No Harmless IDOC archived
Regards,
Raj.

Issue with ALE configuration for creating the idoc for Purchase orders

Hello,
I am trying to send the purchase order through message type configuration using ALE.
I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
I have done ALE distribution using BD64.
Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
In NAST table, the entry is there but on executing RSNAST00 nothing happens.
Please provide me the pointers to solve the given problem.
Regards,
Mayank

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear: g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'. "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'. "Direction
* Receiver
case sy-sysid.
when 'DE2'.
 g_idoc_control_record-rcvpor = 'SAPDE2'. "Port
 g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'. "Partner type
g_idoc_control_record-rcvpfc = ''. "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'. "tRFC Port
case sy-sysid.
when 'DE2'.
 g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'. "Partner type
g_idoc_control_record-sndpfc = ''. "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam = 'E1BPACHE09'.
g_edidd-segnum = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
 exporting
 pi_idoc_control_rec_40 = g_idoc_control_record
* PI_DO_COMMIT = 'X'
* IMPORTING
* PE_IDOC_NUMBER =
* PE_ERROR_PRIOR_TO_APPLICATION =
 tables
 pt_idoc_data_records_40 = g_edidd
 exceptions
 idoc_not_saved = 1
 others = 2.
if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
 in background task as separate unit
 tables
 idoc_control_rec_40 = g_idoc_control_record
 idoc_data_rec_40 = g_edidd.
commit work.
endif.
write: / 'Well done!'.

FM for ORDERS05 Outbound Idoc.

Hi,
I have to post an idoc of basic type ORDERS05 from a custom program.
I have populated the fields for control header and the data section of the idoc.I tried using the FM IDOC_OUTPUT_ORDERS to post the idoc,but when I went and checked in WE05,there were no idoc created.I don't understand why the idoc's are not been created.Could you help me in knowing how to use the FM IDOC_OUTPUT_ORDERS or if there are any other FM's to post an outbound idoc.
Please reply asap.
Thanks,
Sandeep.

Hi,
There is a exit in the FM IDOC_OUTPUT_ORDERS line no 50... double click on the '001' it will take u to the Function Module EXIT_SAPLEINM_001... there click on the Zprogram ...
The FM has EKKO table fields has a Impirting parameter .
u write a code in that Z include program
u have to call the FM MASTER_IDOC_DISTRIBUTE in the program
which creates the IDOC
Thanks,
Manjunath MS

ALE settings for MIRO outbound IDOC

Similar Messages

Maybe you are looking for