IDOC generation and reprint

Dear Experts,
Currently our scenario is as below.
We are using XML for all outputs. once IDOC is generated it is passed to XML port and print is issued.
To reprint IDOC we have a customised program where in we can enter idoc number and print output.
Now we are converting all to smartforms and at some places sapscript. So how to setup reprint for idocs in smartforms and sapscript as it is done for sapscripts. Do we need to make some config in WE19 to issue smart forms and sapscripts.
If possible please give all steps right from preparing structures till reprint.
Can anyone help with detailed solutions.

Goto transaction NACE + button "Output types"
Select one output type and goto folder "Processing routines"
Edited by: Erik Hoven on Feb 26, 2009 10:42 AM

Similar Messages

Idoc generation and reprint for smartforms and sapscripts

Dear Experts,
Currently our scenario is as below.
We are using XML for all outputs. once IDOC is generated it is passed to XML port and print is issued.
To reprint IDOC we have a customised program where in we can enter idoc number and print output.
Now we are converting all to smartforms and at some places sapscript. So how to setup reprint for idocs in smartforms and sapscript as it is done for sapscripts. Do we need to make some config in WE19 to issue smart forms and sapscripts.
If possible please give all steps right from preparing structures till reprint.
Can anyone help with detailed solutions.

Closed as no answer received

Whats the best method to stop IDOC generation and ECC replication?

Hi Gurus,
I would like to do mass data conversion in CRM (adding data origin field for bp's) , during this process i dont want IDOC to be generated and any replication to ECC , how to achive this in tweaking middleware ?
Vinay

Hi
Try tcode SMW3_00 and make an enty into the table with the following:
BDOC_TYPE = BUPA_MAIN
DONOTSEND = 'X'
Paparao Undavali

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

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.

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

Idoc generation

HI All,
If I enter the necessary data in tcode ME21 for purchase order and click on save button, corresponding idoc is to be generated.
This is my requirement.
For this, I worked out and came to know that I have to configure the following steps:
RFC destination, Ports Creation, Partner Profile configuration, Distribution control.
Apart from these, any other configuration is to be done ??
Plz suggest me in what order i have to do all these....
rgds,
anil.

Hi satish kumar ,
Go through the following links
You will find important information about IDOC generation
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Good Luck and reward me for the same
Thanks
Ashok.N

IDOC generation at time to transfer order creation.

What are the config steps involved for idoc generation at the time of transfer order creation?
please advise.
Edited by: avi on Dec 25, 2008 5:31 AM

Hello,
TO creation with respect to Picking perspective:
Lean WM --> output type WMTA can be used to create TO automatically can be created (you can go to NACE transaction and check the settings of WMTA)
From MM WM perspective i think it is PUTAWAY concept, if Purchase order -->Inbound delivery will be created with ref. to inbound delivery TO (putaway) can be created.
Link for IDoc maintenance:
IMG>LE>WM>Interfaces>external systems-->configure wm
link for Automatic TO creation:
IMG>LE>WM>Interfaces>inventory management-->Activate Automatic TO creation
Mahesh
Edited by: Mahesh on Jan 2, 2009 11:19 PM

Provide ALE and IDOC Faqs and all Transactions

Dear Experts,
I am new to ALE & IDOC.
Please provide ALE & IDOCs FAQs and all Transactions?
Thanks in advance.

FAQS
A L E
Q: Our IDOC remains in status 51 ( not posted) while testing ALE setup by passing DEBMAS02 Idocs. The message 'Field KNA1-BRSCH is not an input field'. This is the Industry key. What are we missing?
A: Go to IMG - menu path IMG->LogisticsGeneral-> Logistics Basic Data: Business partners->Customers-> Control->Define Account groups and field selection for customer.
Select sold-to or ship-to. Select General Data. Select control and double click. Industry key is found here. Change the option to 'Optional Entry'.
Check OSS 5599. You may have to update view V_T078D also.
E D I / IDOC
Q:1 We created an EDI Vendor and created all required output conditions. However no IDOC is generated when PO is printed. Why?
A: Go to Header->output for the PO. The output type shall be '6'. The status shall be '1'. If the status is '0' check the timing. If the status is '2' , go to 'GOTO->Processing Log' and the explanation for non-generation of IDOC can be seen.
Q: How can we create / upload IDOC's from legacy system to SAP?
A: Third party tool Mercator may be used to convert Legacy files to Idoc format. Mercator provides an IDOC tree import facility, SAP provides the export facility. You can transfer the Idoc layouts from SAP to Mercator automatically and then map.
Q: We want to receive an outbound EDI 855 IDOC only if E2EDP20 -scheduling confirmation segment is present. Else get an "error" status preventing triggering the EDI subsystem.
A: User exit logic has to be added in function IDOC_INPUT_ORDRSP.
Set up a test flag and set it off when the IDOC header is read.
Turn the flag ON when the EDP20 segment is read.
Interrogate this flag when the next segment after EDP20 in the same IDOC comes in. If it is on ,you have an EDP20 coming in.
Issue an error status 51 with suitable message for whichever condition you don't want the IDOC to be processed, This will stop the IDOC from posting.
Q: Where ever PO is sent to the vendor via EDI, we want an acknowledgement of the PO by vendor. Which fields are updated and what should be my procedure?
A: Execute Program: IDOC_INPUT_ORDRSP
Process code: ORDR
Message type: ORDRSP
IDOC: ORDERS01
The confirmation process allows the supplier to return an acknowledgment. Only Dates and quantities can be changed The information is stored in the PO and can be viewed via Item->Confirmation->Overview. The PO can be flagged as 'confirmation required' so that Pos without acknowledgement receipt can be monitored. Control keys and tolerances (days and quantities) have to be customized.
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 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 ?3 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
STEP 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
-System Name : ERP000
-Description : Sending System
-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
STEP 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
STEP 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)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Reward Points if it helps,
Satish

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

Idoc generation for VL02N

Hi all
I need to create idoc from VL02N on goods issue....
I have one particular output type configured in nace . When that gets triggered i need to create the idoc by taking the outbound delivery number from VL02N and then fetching certain data.
I am confused as to how to approach for this.....Where do i need to write my code for idoc generation so that it can access the outbound delivery number and then do the rest of the processing

Hi,
Your custom function module needs to be defined as the same structure as below.
Local Interface:
*" IMPORTING
*"     REFERENCE(OBJECT) LIKE NAST STRUCTURE NAST
*"     REFERENCE(CONTROL_RECORD_IN) LIKE EDIDC STRUCTURE EDIDC
*" EXPORTING
*"     VALUE(OBJECT_TYPE) LIKE WFAS1-ASGTP
*"     VALUE(CONTROL_RECORD_OUT) LIKE EDIDC STRUCTURE EDIDC
*" TABLES
*"      INT_EDIDD STRUCTURE EDIDD
In function module add following code to get the delivery number.
move object-objky(10) to del_no.
You can see the function module definition of IDOC_OUTPUT_DELVRY which is related to standard outbound process code "DELV".
Regards
Vinod

Outbound IDOC generation

Hi Gurus,
There is a requirement for a customer to develop a custom program i.e. IDOC generation for the Manual payments (F-53 ) raised (As similar to the F110 Automatic payments ).... We are calling MASTER_IDOC_DISTRIBUTION function Module from which IDOC is getting generated but the data which needs to be distubted to XML file through Port configuration is not happening .
with the Automatic payments with same port configuration this is working fine.... so is that anythign we need to do in the custom program ...
Thanks for your help in advance
Thanks & Regards,
Ramamurthy

Hi Ramamurthy,
I'm assuming that the IDoc gets generated, i.e. you can see it in WE02. If not then you're probably missing the entry in the distribution model (BD64), so the function module creates a master IDoc, but no communication IDocs.
If you see the IDocs on the database, but they are not being sent, check if your custom program issues a COMMIT WORK. Alternatively you could also see if changing the partner profile from Send immediately to Send via background program and then sending the IDoc via RSEOUT00 makes a difference.
Cheers, harald

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

Automatic IDOC generation !

How to automate an idoc generation when the credit memo is created !
Can any one tell me the approach and the steps !

Hi,
You dont need to write a code in userexit, just check this IDOC type : GSVERF01.(TCODE: WE60 or WE30)
Thru this you can create an IDOC for Credit memo.
Thru message control option we can achieve that.
Read this.. it will help u.
Message Control
The objective of Message Control is the exchange of information between various partners and the launching of subsequent processing that is partner-independent. Message Control provides interfaces to make this possible.
You can use the Message Control interfaces to describe various data combinations along with the required processing. If one of these data combinations is found to be applicable during the processing of an application object, the appropriate processing is started (synchronously or asynchronously).
Message Control is a "service program" for other applications. It is initiated via ABAP function modules. Information about which programs carry out the subsequent processing is managed in tables . The conditions determining when programs are called are often very complex and also depend on the individual customer situation. Message Control offers the flexibility needed to represent these various situations .
Purpose
The output or follow up processing of partner-dependent messages is automated via Message Control. The application then calls the Message Control via the specified interfaces.
You can use these interfaces to describe various data combinations along with the required processing. If one of these data combinations appears during processing, the appropriate processing is started (synchronously or asynchronously). You can define processing with several different methods, for example as a workflow, print output or as an IDoc dispatch for EDI.
Implementation considerations
SD and MM applications always use Message Control for message output. You carry out Customizing of the Message Control in the applications Customizing. The Message Control is also sometimes described here as "output control".
Integration
Message Control is a "service program" for other applications. It is initiated via ABAP function modules. An application that uses Message Control must
Call the Message Control
Transfer files which should be compared with the combinations defined in Customizing.
Provide a processed program, that is called from the Message Control, if the transferred data corresponds with the combinations defined in Customizing
Features
The condition technique in the R/3 System is used to formulate the data combinations required. If the current application data corresponds to the conditions defined in Customizing, message determination was successful and created a message default. If the application supports it, the proposal can be changed (processed).
As a result the message is processed immediately or at a defined time. The processing status of the message is stored in a status record. If the application supports it, a processing log is written as well.
Message Control scenarios:
1. The credit limit has been exceeded in a sales order, whereupon the block indicator is assigned. The Message Control should respond to the block indicator by printing out this customers account history.
2. A document is released and receives a corresponding status in its data record. The Message Control should thereupon issue a release message.
There are also applications which can "switch off" message determination and directly generate the message default.
Structure
Condition Components and Condition Records
The individual objects of the Message Control which are relevant in the message determination process and can be configured in Customizing or the application transaction are explained.
Message determination
This section describes how the condition component hierarchy is evaluated and how the condition tables are accessed. Different scenarios, which can be realized by special strategies when Customizing the condition component, are used as examples.
Message Default and Message Editing
The result of message determination is a message default that can be edited manually in the application, if this function is available in the application. If not, any messages found are forwarded directly for automatic processing.
Message processing
This explains how the message found can be processed.
Regards.

IDOC generation and reprint

Similar Messages

Maybe you are looking for