Doubt Regarding IDOC generation

IDocs are used for asynchronous transactions: each IDoc generated exists as a
self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
where can i see the generated IDOC's in R/3.
whether IDOC will be generated with each and every transaction in R/3.

Hi Govada
prabhu can we find IDOC's date wise
Answer : In WE03 select the date which you want.
Is it compulsary for each transaction in SAP that and IDOC generates... like Purchase Order Creating, Stock maintainance etc.,
Answer: NO not all trancastion create IDOCs
can we check like for purchase order today how many IDOC s are generated
Answer: Yes goto WE02 and give the IDOC name select the date of today you see all
Do we have to configure some thing to generate IDOC or for each bussiness action a IDOC will will be genarated
Answer : We need to configure.
whether every IDOC stores in R/3 if where the IDOCs will be stored in R/3, how can we see the what are all the required feilds for particular segment of IDOC
Answer : IDOC data are stored in database . goto WE30 and see which field are mandotry.
Please Reward points
Regrads
Sreeram.G.Reddy

Similar Messages

Doubt Regarding IDoc Adapter

Dear Gurus,
In IDoc to XML conversion scenarios, we never use Sender Communication Channel because the IDoc adapter sits on the ABAP stack and the conversion is done by the IDoc adaper in the Integration Server.
Then why in case of the reverse scenario , i.e. XML to IDoc conversion we use Receiver Communication channel and the IDoc adapeter explicitly? Why can't that IDoc Adpater that sits on the ABAP stack convert the xml file into IDoc format?

Hi Shweta,
the reason for this is:
The adapter at the inbound channel is located before the Integration Server pipeline and calls this pipeline. The adapter at the outbound channel, however, is called by the pipeline, and can therefore be regarded as part of the pipeline.
The connected systems transfer or receive IDocs through their IDoc RFC interface.
if you check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
and read the Integration section and try to understand the pipeline flow, as the names are not understandable(viz. receiver determintaion, mapping etc.) in the diagram.
you will get the clarity after reading this..
Sachin

Doubt Regarding validation of IDOCS

Hi Gurus,
I have some doubts regarding IDOCS.
1. If we are sending a IDOC from XI to R/3, where does we do validations from R/3 side and how do we do that. Suppose if we are sending a Purchase order IDOC form XI to R/3, how to do validations for that particular IDOC for PO number and some other fields from R/3 side.
2. Do we need to do validations in a aABAP Program.
please clarify me these Questions. Thanks in advance..
santosh.

Hi Santhosh,
If you want to do any validations in ur IDOC,then from XI just push the IDOC,dont post it.
(ie)Send the IDOC from XI in status 64 :IDoc ready to be transferred to application.
Once R/3 Received this status then thru your ABAP progream just get this IDOC no: and do the validations then Post the IDOC manually.
Thanks.
Note:Reward Points if you find useful.

Idoc generation for message types

Hi All,
regarding IDOC generation....
how do we activate the message type so that every time the application data which is created or changed or deleted generates the idoc and send it to other system. If iam not using Chnage pointers technique then i would not be activating the message type in BD50. In such case ie if the message type is not present in BD50 list and if change pointers is not used to transfer that message type . How do we genrate the idoc for such message types.
Thanks
Avinash

Hi,
For ur scenario u need to go for change pointers method only.U have other options like distributing master data and transactional data..But i don't think anything otherthan change pointers is useful.
Regards,
Nagaraj

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

Doubt in IDOC's - Process Codes

Hi,
Currently i am working on an object related to IDOC generation. This is my first object in IDOC's. I am doing it from the scratch including creation of segments, IDOC type, message type, process codes...
In this process, I am developing a function module that should be assigned to the process code. My doubt here is, is there any standard interface to the function module that we have to assign to the process code?
I am also giving the flow which i will be using in developing the Function module. Please go through it and kindly let me know if I am doing it in the right way or not?
1. Extract data from data base based on the entry in NAST
2. Filling IDOC DATA & Control records
3. Calling the FM MASTER_IDOC_DISTRIBUTE to generate the IDOC
Please suggest me whether i am doing it in the correct way or not?
Thanks in Advance,
Best Regards,
Phani

Hi,
For outbound u need to attach ur FM to the process code in WE41 tcode..I think u r using message control method for ur requirement.please look at the configurations for outbound using message control method.we use we41 (outbound process code) and we use this in the message control tab in the partner profiles.
The transaction codes that are required for this method are
We81
We30
We31
We82
We21
We20
Bd64
Nace
Me22n (purchase order), va02 (sales order) etc.
Ex: purchase order.
Message type: ORDERS
Idoc type: ORDERS05
Outbound process code for purchase order: me10
Regards,
Nagaraj

Inbound Idoc Generation

Hello All,
We have a ALE concept to transfer data between clients. We have made the settings and the process was fine. But on some days Inbound Idoc is not getting generated with respect to the outbound Idoc, and after some times once again system comes to normal state and the idoc generation is fine. How ever we dont have any root cause for the failure of Idoc generation. Could someone let me know where i can chk the info and what all the parammetres needs to be checked.
Note ; There are no issues in ALE ocnfig settings.

Hi ,
See the following code :
Program To Generate IDoc
*& Report ZZ_Program_To_Create_Idoc
report zz_program_to_create_idoc .
tables: ekko,ekpo.
selection-screen skip 3.
selection-screen begin of block b1 with frame title titl.
selection-screen skip.
select-options s_ebeln for ekko-ebeln.
selection-screen skip.
selection-screen end of block b1.
data: header_segment_name like edidd-segnam value 'Z1EKKO',
 item_segment_name like edidd-segnam value 'Z1EKPO',
 idoc_name like edidc-idoctp value 'Z19838IDOC1'.
data: header_segment_data like z1ekko,
 item_segment_data like z1ekpo.
data: control_record like edidc.
data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
data: i_communication like edidc occurs 0 with header line,
 i_data like edidd occurs 0 with header line.
data: begin of i_ekko occurs 0,
 ebeln like ekko-ebeln,
 aedat like ekko-aedat,
 bukrs like ekko-bukrs,
 bsart like ekko-bsart,
 lifnr like ekko-lifnr,
 end of i_ekko.
data: begin of i_ekpo occurs 0,
 ebelp like ekpo-ebelp,
 matnr like ekpo-matnr,
 menge like ekpo-menge,
 meins like ekpo-meins,
 netpr like ekpo-netpr,
 end of i_ekpo.
start-of-selection.
select ebeln aedat bukrs bsart lifnr from ekko
 into table i_ekko where ebeln in s_ebeln.
select ebelp
 matnr
 menge
 meins
 netpr
 from ekpo
 into table i_ekpo
 where ebeln in s_ebeln.
control_record-mestyp = messagetyp.
control_record-rcvprt = 'LS'.
control_record-idoctp = idoc_name.
control_record-rcvprn = '0MART800'.
loop at i_ekko.
header_segment_data-ebeln = i_ekko-ebeln.
header_segment_data-aedat = i_ekko-aedat.
header_segment_data-bukrs = i_ekko-bukrs.
header_segment_data-bsart = i_ekko-bsart.
header_segment_data-lifnr = i_ekko-lifnr.
i_data-segnam = header_segment_name.
i_data-sdata = header_segment_data.
append i_data.
select ebelp
 matnr
 menge
 meins
 netpr
 from ekpo
 into table i_ekpo
 where ebeln = i_ekko-ebeln.
loop at i_ekpo.
item_segment_data-ebelp = i_ekpo-ebelp.
item_segment_data-matnr = i_ekpo-matnr.
item_segment_data-menge = i_ekpo-menge.
item_segment_data-meins = i_ekpo-meins.
item_segment_data-netpr = i_ekpo-netpr.
i_data-segnam = item_segment_name.
i_data-sdata = item_segment_data.
append i_data.
endloop.
clear i_ekpo.
refresh i_ekpo.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
 master_idoc_control = control_record
OBJ_TYPE = ''
CHNUM = ''
tables
 communication_idoc_control = i_communication
 master_idoc_data = i_data
exceptions
 error_in_idoc_control = 1
 error_writing_idoc_status = 2
 error_in_idoc_data = 3
 sending_logical_system_unknown = 4
 others = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
loop at i_communication.
 write: 'IDOC GENERATED', i_communication-docnum.
endloop.
commit work.
endif.
initialization.
titl = 'ENTER THE PURCHASE ORDER NUMBER'.
Reward points if helpful.
Regards.
Srikanta Gope.

Any BADI returning the 'IDOC Status' during IDOC generation.

Hello All,
I need a BADI which is being called during any IDOC generation and which returns the 'IDOC Status' i.e. Pass/Fail etc.
So far I am able to find BADIs like 'IDOC_DATA_MAPPER' or ''IDOC_DATA_INSERT'' but such BADIs only return the IDOC document number.. they do not return any information on IDOC Status (the field Status field remains blank).
Can any one suggest some solution on this please.
Regards
Vikas Gupta

Hi Erik,
Thanks for your reply, though i was able to get the status from BADI IDOC_DATA_MAPPER itself (earlier there were some config issues...which were creating some problems) but thanks for letting me know about table EDIDS, it helped at places.
Regards
Vikas Gupta

F110 Idoc generation

hi Folks,
i want to generate an idoc PEXR2002 using transaction f110 ( automatic payment program)
Does anybody have any idea on how to do it. your inputs are valuable.
Regards,
Padma

hi Madhu,
thanx for your input. I checked all the settings. they are in place.
In the additional log I am getting following entries:
06-06-2008 12:36:51 payments by EDI / IDoc generation
06-06-2008 12:36:51 IDOcs were generated for the following entries
06-06-2008 12:36:51 Company code 3001 House bank AMX Payment method W
06-06-2008 12:36:51
06-06-2008 12:36:51 End of log
06-06-2008 12:36:52 Step 002 started (program SAPFPAYM_SCHEDULE, variant &0000000000019, user ID SACHIN)
06-06-2008 12:36:52 Step 003 started (program RFFOEDI1, variant &0000000000012, user ID SACHIN)
06-06-2008 12:36:52 Program RFFOEDI1: No records selected
06-06-2008 12:36:52 Job finished
Regards,
Padma

LSMW error message during "Start Idoc generation"

Hi ,
I am getting error message "'/tmp/YS.lsmw.conv' File Has Not Been Accepted for Processing"
during the step "Start Idoc generation" in transaction LSMW.
Please help to solve this issue.
Thanks & regards,
Yogita

Hi,
I already have set port and partner function.
As per the details of the error message, it says "
System Response
Clarify if the inbound file is a Unicode file.
Procedure
If it is not a Unicode file, change the port definition and then start inbound processing again.
If it is a Unicode file, then the file must be generated with the 'EDI_DC40_U' indicator. This must be clarified with the creator of the file.
I have added the check Unicode fomat while defining the port.
Can you please help?
Regards,
Yogita

Doubt on IDOC TO IDOC communication

Hi Experts,
I have a doubt on IDOC to IDOC communication:
Plz clarify it
1. what is the need of passing same IDOC from one system to other system through XI while communicating between two systems,it can be done by using ABAP also ?
2.what is the advantage of passing like this through XI compared to ABAP?
                       Plz clarify good answers will be rewarded .
                                                                                Regards,
                                                                                Vinod.

Hi,
See when you are dealing with Only IDOC to IDOC Communication means there is no need of XI here.
You can go with ALE also here.
Situations to go to XI.
1) when you have the Different field mappings
2) When you are having the multiple receivers
3) when you are dealing with Bundling & Transformations
Reward Ponts If Helpful
Regards
Giri

Doubt on IDOC communication

Hi Experts,
                  I have a doubt on IDOC to IDOC communication:
Plz clarify it
                    1. what is the need of passing same IDOC from one system to other system    through XI while communicating between two systems,it can be done by using ABAP also ?
                     2.what is the advantage of passing like this through XI compared to ABAP?
               Plz clarify good answers will be rewarded .
                                                                                Regards,
                                                                                Vinod.

The need for an XI to transfer IDOC from one system to another sytem : the answer for this comes from the basic of using XI as a middle ware.
1. When you connect IDOC directly to another system without using XI....you are going for P2P connections then this leds to problem in monitoring if the data breaks, you have to login to both systems to check......
2. we have a central monitoring tool for check this iterface..
3. You can build a message orchestration using the BPM if required for this IDOC...
4. You can have full control in the IDOC processing...i mean do you want to send ot not and so on.
Beofre XI or typical connection between 2 SAP Systems were using IDOC directly but they are P2P connectinons,,,no control, no monitoring....NO orcheatreation...etc.....

Doubts regarding Alerts in XI

Hi ,
I have couple of doubts regarding XI Alerts .
1) How to raise Alerts in ABAP Sender proxy . Say for example if sender
 ABAP proxy fails to send message how to raise alert . please provide steps
 how we can achieve this task.
2) How to raise Alerts in IDOC Scenario . How to raise ALERTS if IDOC
 fails in sender or receiver R/3 system.

Hi,
Have a look at this.
http://www.****************/Tutorials/XI/AlertConfiguration/AC1.htm
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
Refer this also
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Reward points if find useful.
Message was edited by:
 Akshay Jamgaonkar
Message was edited by:
 Akshay Jamgaonkar

C202 idoc generation

Hello All,
I have a requirement like this.
For transaction C202, (Master recipe change), when I go to Materials->BOM and change material quantity,
and save the document, an idoc should be created. We hve Idoc type, Message type and Object type copied from BOM001 as customized.
How can I achieve this. In NACE, I hve done changes for application (p1) ->medium (A) and processing routine ALE_processing and program RSNASTED for output type ME01.
But idoc is not getting created when I change BOM quantity and SAVE the document.
Am I missing something here? I am not linking the object type (BOR) anywhere. Is this an issue?
Any help and detailed explanation step-by-step what to do to achieve idoc generation would be appreciated.
Thanks
Ricky

Hi,
For ur scenario u need to go for change pointers method only.U have other options like distributing master data and transactional data..But i don't think anything otherthan change pointers is useful.
Regards,
Nagaraj

Reg: Idoc generation

Hi All,
AS per my understanding for SPEC2K idoc generation, SAP generates two IDOCS. one of standard SAP message type and another is of SPEC2K type .
My requirement : if the customer requested items are not available then both the SAP message IDOC and SPEC2K idocs should be generated.
If the customer requested items are available then only SAP message type idoc should be triggered and SPEC2K idoc should not be triggered.
Is there any settings by which I can achive this.
Thanks in Advance.
Vijay.

Go through the following Steps
Try with the follwoing steps
Sending System(Outbound ALE Process)
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Create Model View
Tcode BD82 ¡V Generate partner Profiles & Create Ports
Tcode BD64 ¡V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ¡V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 ¡V Send Material Data
Tcode WE05 ¡V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Thanks & regards
Sreenivas
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Thanks & Regards
Abhay.
rewards point

Doubt Regarding IDOC generation

Similar Messages

Maybe you are looking for