Output via idoc/ale

Hello Guru's
creating output for billing docs via idoc.
Just one more question, I am doing this output via medium 6 and date 4 (send immediately) now since my output is founf in the billing doc and it is saving properly what is my next job to create the programme?
If you can tell me what would be the next process to see and maintain.
I have maintained port, partner profile, distribution model also.
Thanks
Aman

Hi,
Goto the T.Code NACE.
Select your appropriate output type.
Click on Details.
Goto Processing routines.
Maintain the medium as "6(EDI)" and program as "RSNASTED" and Form routine as "EDI_PROCESSING".
Please check with your ABAPer to trigger the IDOC.
Regards,
Krishna.

Similar Messages

Data Fir IDOC ALE and EDI

Hello All,
    I am newly join in IT company (Name don't want to specify) . They have putted me in a consolidate project in which I do have to work on IDOC,ALE and EDI object.
yet in my career with SAP ABAP I haven't work on the above mention terms of SAP. Can some One please guide me and provide me some material to prepare my self best for the things.
Regards
Swati Namdev

Some use full Tcodes:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
WE02     List Of All Idocs Created. (Default, Additional, EDI)
WE05     List Of Idocs Created.    (Standard, Additional)
WE06     Active Monitoring For Idoc Processing.
WE07     Idoc Statistics.
WE08     Display View u201CFile Statusu201D:Overview-Path Name.
WE09     Idoc Search For Business Contents (Database).
WE10     Idoc Search For Business Contents (Archive).
WE12     Modification Of Outbound File, Triggering Inbound Processing.
WE14     Process All Selected Idocs.
WE15     Selection Program For Issuing Output.
WE16     Trigger Inbound Processing.
WE17     Trigger Status Processing.
WE18     Generate Test Status File For Outbound Idocs.
WE19     Test Tool For Idoc Processing
WE20     Partner Profile.
WE21     Ports In Idoc Processing.
WE23     Display Test Catalog Test Idoc Interface.
WE24     Maintain Table View. Direction-1.(Outbound)
WE27     Maintain Table View. Direction-2.(Inbound)
WE30     Develop Idoc Type.
WE31     Develop Idoc Segments.
WE32     View Development.
WE33     Maintain Table Views.
WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40     Display System Process Code.
WE41     Display View: Logical Msg Overview. For Outbund.
WE42     Display View: Logical Msg Overview. For Inbound.
WE43     Display Status Records.
WE44     Display Partner Types
WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46     Global Parameter For Idoc Interface.
WE47     Status Maintenance.
WE50     Display Text For Process Code System.
WE54     Idoc Function Module For File Name
WE56     Display Status Process Code
WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58     Text For Process Code Status.
WE60     Documentation For Idoc Type.
WE61     Documentation For Idoc Record Type.
WE62     Documentation For Idoc Segment Type.
WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
WE64     Process Code In Idoc Inbound And Outbound.
WE70     Conversion Table For Basic Types.
WE71     Conversion Table For Extensions.
WE72     Conversion Table For Field DOCTYP.
WE73     Conversion Table For Logical Message Type.
WE81          EDI:Logical Message Type.
WE82     Message Types And Assignment To Idoc Types.
WE84     Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
BD10     Send Material (Matmas)
BD11     Get Material.
BD12     Send Customer.
BD13     Get Customers
BD14     Send Vendor.
BD15     Get Vendor.
BD16     Send Cost Center. (Cosmas)
BD17     Request Cost Center.
BD18     Send G/L Accounts.
BD19     Get Master Data G/L Accounts.
BD20     Inbound Processing Of Idocs Ready For Transfer.
BD21     Creating Idoc Types For Change Pointers.
BD22     Delete Change Pointers.
BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24     Send Cost Elements.
BD25     Send Activity Type (COAMAS)
BD26     Request Activity Type
BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28     Cost Center/ Cost Elements: Send Control Records.
BD30     Material Bom Distribution. (Bommat).
BD31     Document Structure Distribution. (Bomdoc)
BD32     Plant Allocation To Material Boms Distribution.
BD33     Distribution Of Material Variants. (STTMAT)
BD34     Distribution Of Boms (BOMORD)
BD35     ALE: Send Business Process Group.
BD36     ALE: Send Business Process.
BD37     ALE: Send Business Process Price.
BD40     Generate Idocs For Serialization Group From Change Pointers.
BD41     Dispatch Of Idocs Of Serialization Group.
BD42     Check Dispatch Status Of Idocs Of Serialization Group.
BD43     Processing Inbound Idocs Of Serialization Group.
BD44     Change View u201CSerialization Groupu201D.
BD47     Dependence Between Methods.
BD48     Dependence Between Methods And Message Type.
BD50     Activate Change Pointers For Message Type.
BD51     Characteristics Of Inbound Function Module.
BD52     Determine Work Area.
BD53     Reduce Message Type.
BD54     Change View: Logical Systems
BD55     Idoc Conversion.
BD56     Maintain Idoc Segment Filters.
BD57     Link Type And Serialization Type Of Message Type.
BD58     Convert Organizational Unit.
BD59     Allocation Of Object Type.
BD60     Additional Data For Message Type.
BD61     Activate Change Pointers Generally.
BD62     Display Conversion Rule.
BD63     Transport Of Ale Tables For A Message Type.
BD64     Display Distribution Model.
BD65     Maintain Idoc Type Required Fields.
BD66     Change Idoc Fields.
BD67     Function Module For ALE/EDI Overview.
BD68     Maintain List.
BD69     Assignment Of Idoc Type To Message Type.
BD70     Cross-System Comparison Of Number Range Objects.
BD71     Attributes For Receiver Determination.
BD72     Active Events For ALE/EDI
BD73     Start Error Handling For Non-Posted Idocs.
BD75     Status Conversion With Trfc Execution.
BD77     Generate Transport Requests For Distributing ALE Customizing Data.
BD78     Monitoring Ale Customizing Data Transport
BD79     ALE IDOC Segments - Conversion Rule
BD81     Filter Objects For BAPI Parameter Filtering
BD82     Generating Partner Profile
BD83     Re-Processing Incorrect Outbound Odocs.
BD84     Re-Processing Of Idocs After ALE Input Error.
BD85     Consistency Check: Reassignment Between Two System.
BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
BD87     Select Idocs
BD89     Customizing Data Modeling For Distribution Model.
BD91     Distribute All Characteristics Via ALE.
BD92     Distribute Class Via ALE: Send Direct.
BD93     Distribution Of Classification Data Via ALE.
BD95     Ale Object View
BD96     Filter Object For Receiver Determination Of Methods.
BD97     Assign RFC Destination For Synchronous Method Calls.
BD98     Consistency Check With Workflow Link
BD99     Dependencies Between Message Types.
BD100     Display Serialized Idocs. (Serialization Using Object Types)
BD101     Serialization Using Object Types: Consistency Check.
BD102     Ale: Outbound Channel Registry.

Error message mes when trying to send PO via IDOCS to another system?

Hi Abap expert,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system.
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi,
Go and check it in NACE tcode, whether , Condition type, output types are maintained or not? if not maintained, Maintain it for 6 -PO for EDI.
Hope this is the error you are getting.
Thanks
Manju

Name of the Programme, PO output medium IDOC writes to a File

Hello Guru's,
Will anyone know the name of the Program which writes the Purchase Order Output Medium IDOC into a file ( xl file, text file etc,.) in SAP.

Output in this manner is controlled via Output control and program RSNASTED routine EDI_PROCESSING.

Script output through Idoc

Hi,
Can i send my script output through Idoc?
Thanks,
Sreenivas

Hi,
If u check in NACE selecting appl and output types tab
and processing routines u can find these
medium
1 --- printoutput
2 --- fax
6 --- EDI
A --- Distribution(ALE) what does these last two mean for
i think it can be possible?
Please check this and make me clear.....
Also give rply how to justify that we cant send....
Thanks & Regards
Sreenivas

IDOC/ALE/BAPI/BADI

Hi,
I want to understand the difference between IDOC/ALE/BAPI/BADI in context to a functional consultant.what is the role of each with an EXAMPLE.I want to basically understand with examples w.r.t SD or MM instead of theory which i could get in forum.
What is the role of a functional SD consultant, in these technology mentioned?
If i have to Test a BAPI or BADI what is that i should test???what is the T codes to be tested ? How to go about it??
Like in case of Order to cash testing, i will check if the sales cycle runs well, using T codes, Va01, vl01n, vf01.
Awaiting reply.
Thanks
LK

Hi Lekshmi,
I want to understand the difference between IDOC/ALE/BAPI/BADI in context to a functional consultant.
what is the role of each with an EXAMPLE.
I want to basically understand with examples w.r.t SD or MM instead of theory which i could get in forum.
What is the role of a functional SD consultant, in these technology mentioned?
Idoc/ALE/BAPI/BADI are basically advanced functionalities available in ABAP. These are treated as seperate module by somebody as "Cross Applications".
If we get in
IDOC is the concept which works for Third party communication from SAP.
Scenarion 1:
For example: I am a Buyer from your Company and i don't have SAP system where you have SAP Practice. I had given you one Order for which i need Confirmation and it needs to understand by my system. In this case IDOC is useful to transfer the confirmation details to my system understandable language. This can be acheived by any other outputs like e-Mail/Printout/Fax. But for these kind of Outputs thers is one limitation. those are in document form means if you take the print out it confirmation can be taken as a print out as a hard copy or soft coy by saving into PDF format. but that data cannot be accessed by my system to convert that data for further my own reporting purpose. if we use IDOCs.
These Idocs are transferred through Middleware and reach third party system (in this example my own system which does not have SAP) and store the details. later i can use that data how ever i can for my internal reporting purpose.
Scenario 2:
ALE: ALE also works like above, but the difference is this works for SAP-SAP communication. if i take the above example.... I have SAP System being a buyer and you have SAP sytem. Order Confirmaiton come from your system to my system.
If i have to Test a BAPI or BADI what is that i should test???what is the T codes to be tested ? How to go about it??
Like in case of Order to cash testing, i will check if the sales cycle runs well, using T codes, Va01, vl01n, vf01.
There is no such tcodes to test the enhancement functionality.
I assume you knows SAP SD.
If i take the example of SD Sales Order.
PO Number field is to explain the enhancement testing.
Your client enhanced the functionality of PO Number for which you are doing the testing for example.
now you get inside of the VA01 transaction and put all the headeer data and PO Number and press enter.
then based on the enhancement functionality system will act.
For example.. you had given AAA111 for Customer 123456.
You have entered Inside of VA01 and entered Sold and Shipto numbers as 123456. then entered PO number as BBB111 and press enter.
As per the enhancement you suppose to enter PO number as AAA111 for customer 123456, but you entered as BBB111.
Based on your enhancements system will through the error saying you entered wrong PO Number.
This is the testing part usually Functional Guy do.
Please let me know if you have any further clarification
Thanks & Regards
Venkat

Idocs ale and edi

Hello Experts,
       I am beginner in IDOCS,ALE AND EDI concepts, i would appreciate if some one can forward me material on these concepts, also some sample programs or examples on these.
Thanks.
Raghu

Hi,
ALE Process Steps:
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
IDOC
Check these links.
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
EDI
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
reward points if useful
regards,
ANJI
Message was edited by:
        Anji Reddy Vangala

RFC, IDOC, ALE, BAPI

HI everybody,
anybody can tell me
1.what is RFC and its use?
2.What is IDOC and its purpose?
3.What ie ALE and BAPI? please tell me their functions.
points will be rewared.

IDocs are simple ASCII data streams. When they are stored to a disk file, the IDocs
are simple flat files with lines of text, where the lines are structured into data fields.
The typical structured file has records, each record starting with a leading string that
identifies the record type. Their specification is stored in the data dictionary.
IDocs is the acronym for Interchange Document. This indicates a set of (electronic)
information which builds a logical entity. An IDoc is e.g. all the data of a single
customer in your customer master data file, or the IDoc is all the data of a single
invoice.
IDoc data is usually exchanged between systems and partners that are completely
independent. Therefore, the data should be transmitted in a format that can easily be
corrected by the computer operators. It is therefore mandatory to post the data in a
human readable form.
Nowadays, this means that data is coded in ASCII format, including numbers which
are sent as a string of figures 0 to 9. Such data can easily be read with any text editor
on any computer, be it a PC, Macintosh, UNIX System, S/390 or any internet
browser.
The information which is exchanged by IDocs is called a message and the IDoc is
the physical representation of such a message. The name messages for the
information sent via IDocs is used in the same ways as other EDI standards. .
Everybody who has ever dealt with interface programming, will find IDocs very
much like the hierarchical data files used in traditional data exchange.
International standards like the ODETTE or VDA formats are designed in the same
way as IDocs are.
Other EDI standards like XML, ANSI X.12 or EDIFACT/UN are based on a data
description language. They differ principally from the IDocs concept, because they
use a programming language syntax (e.g. like Postscript or HTML) to embed the
data.

ME23N Error when trying to send PO via IDOCS to another system?

Hello Experts,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system (XI)
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

I just got the same problem. Everything worked fine when i was using message type ORDERS01, but when i changed it to ORDERS05 this problem started happening.
This might solve your problem. If you have it solved out can you tell us the solution you found??
regards,
Diogo

T-code ME23N message when trying to send PO via IDOCS to another system?

Hello MM Experts,
I am not sure if my question is more for ABAP guys , but since it is MM related I decided to share it with MM experts as well.
I am getting wired message what I am trying to send PO via IDocs to other SAP system (XI)
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi Boby ,
TRY going thru this link and check for the details given in it wether they are in place or not specially in the message controls, viz: application EF ,message type NEU and process code ME10
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
regards
kp

Creating HR objects via IDoc HRMD_A05

Hi to all
I want to create HR objects via IDoc HRMD_A05 and want the objects numbered using INTERNAL number range.
The IDoc documentation says to pass an exclamation mark '!' to OBJID to make the system generate new number. However, the field is numeric and can not contain '!'.
Has anybody tried this way before and achieved to create objects numbered internally?
Thanks

Hi
I have told the issue to the SAP OSS and their feedback was:
"As explained in note 741165:
'There is no provision to carry out an internal number assignment using
ALE in the target system. Therefore, the numbers must be assigned when
the IDOCs are created in the source system.'
The documentation in the Interface Repository is wrong.
Regards
*--Serdar

Outputting via SDI to DigiBeta thru Blackmagic Decklink Extreme

I'm running Final Cut Pro 5.1.2 on MacOS 10.4.8. I've edited a 23.98FPS - DVCPro50 sequence. I can preview using the Decklink Extreme card fine. I can output via compenent out to a regular beta deck (UVW-1800) just fine, which is also the deck I use for monitoring while I am editing. I plug the SDI output from the decklink card into our digibeta deck (DVW-A500). I also send the audio over SDI. I see both the audio and video in my digibeta deck. If I just PLAY the sequence out, the digibeta sees and hears it fine. No problems.
This is my problem. Whenever I try to 'edit to tape' it usually starts out fine... then I get A LOT of digital drop outs / squares / digital distortion on the digibeta. They come up randomly and it also digitally distorts the audio when you play the tape back.
The digibeta deck is fine, as we use it to output via our Avid Media Composers every day...no dropouts or problems. It has to be with FCP / DeckLink Card when you try an 'edit to tape'. I've also tried a 'print to video' with the same results. Have you guys heard of this problem at all? Hopefully you have a fix for me...
thanks.

Awesome - the Out Ref fix did it!
When I did the edit to tape I tried both insert editing and assemble editing - both ended up the same.
On a side discussion - how do you sync the FCP machine with the black burst generator? I'm still a bit new to this - what exactly does the genlock do on the Decklink Extreme card? Is this where I sync with the black burst?
I assume the digibeta deck will also get synced with the same black burst generator. Does this go into the reference input on the back?
Thanks for your help,
-Grant

Help with sound output via HDMI

My sound output via HDMI suddenly stopped worked to my TV set. I've reset the PRAM and the SMC. When I go to sound control panel for sound output, the setting is on Headphones. When I try to change it to SV420XVT1A (the tv) it immediately jumps back to headphone. I also tried a different HDMI cable to a different HDMI port on the tv. This just started after the Mac Mini had been turned off for a week. I'm using Lion and it's an 8GB Intel Core 2 Duo. Any suggestions?

I actually discovered this answer about 5 minutes after I posted the question. Thanks a lot for your help!! Funny thing is that it had worked all along with something plugged in the headphone jack but suddenly stopped working. Again, thanks!

Sending report output via E-mail (excel pivoted format)

Hi all,
i have a written a report where i need to send the report output to somebody via
E-mail.i am sending this report output via E-mail successfully.The receiver receives, my output in excel format.but this excel is not pivoted.
i want , the receiver should get my output in pivoted excel format.i.e my output data should be exactly fit in the excel sheet.
now the columns in excel sheet are overlapping.once i double clicked, the columns are getting separated.i do not want to double click.i want all the columns should come properly i.e excel field length should be adjusted as per the output field length.
i am giving my coding below.plz suggest how i can do the above thing .it's urgent.
any idea will be highly appreaciated.
Regards
if not p_email1 is initial.
 perform fill_report_csv.
 perform f_send_internet_mail.
endif.
FORM fill_report_csv.
 data : l_text(232) type c,
 v_matnr1(21) type c,
 v_matnr(21) type c,
 v_matkl(14) type c,
 v_maktx(45) type c,
 v_ttlstk(14) type c,
 v_verpr(14) type c,
 v_werks(14) type c,
 v_lgort(14) type c,
 v_char(10) type c,
 v_stks type p ,
 v_po(40) type c,
 v_qty(13) type c,
 v_qty1 type sy-datum,
 v_date(15) type c,
 v_date1(15) TYPE C,
 v_name(35) type c,
 v_eknam(18) type c,
 v_lifnr(15) type c,
 l_po(40) type c,
 v_matnr(20) type c,
 l_rate(11) type p decimals 5,
 l_flag type c.
concatenate c_equal c_colon 'PO no.' c_colon
 into v_po.
concatenate c_equal c_colon 'Material no.' c_colon
 into v_matnr.
concatenate c_equal c_colon 'Description.' c_colon
 into v_maktx.
concatenate c_equal c_colon 'Due Qty.' c_colon
 into v_qty.
concatenate c_equal c_colon 'Del Date.' c_colon
 into v_date.
concatenate c_equal c_colon 'Vendor.' c_colon
 into v_name.
concatenate c_equal c_colon 'Buyer.' c_colon
 into v_eknam.
concatenate c_equal c_colon 'Vendor Code.' c_colon
 into v_lifnr.
concatenate
 v_po v_matnr v_maktx v_qty
 v_date v_name v_eknam v_lifnr
 into i_download
 SEPARATED BY con_tab.
append i_download .
clear : v_po,v_matnr, v_maktx, v_qty, v_date, v_name, v_eknam,v_lifnr .
clear wa_output.
loop at i_output into wa_output.
 on change of wa_output-ebeln.
 clear v_lines.
 loop at i_eket into wa_eket
 where ebeln = wa_output-ebeln.
 v_lines = v_lines + 1.
 clear wa_eket.
 endloop.
**-- Checking of page break
 v_lines = sy-linno + v_lines .
 if 55 < v_lines .
 write:/0(161) sy-uline.
 new-page.
 endif.
clear v_lines.
 loop at i_eket into wa_eket
 where ebeln = wa_output-ebeln.
 v_lines = v_lines + 1.
 clear wa_eket.
 endloop.
*-- Calculating the due qty.
 wa_output-dumng = wa_output-menge - wa_output-wemng.
*-- Writing the Line items of the PO.
 read table i_ekpo into wa_ekpo
 with key ebeln = wa_output-ebeln
 ebelp = wa_output-ebelp.
 l_rate = wa_ekpo-netpr / wa_ekpo-peinh.
*-- Writing of PO detail
 if wa_output-dumng gt 0 .
 v_qty = wa_output-dumng.
 v_date1 = wa_output-eindt.
 v_maktx = wa_output-maktx.
 if wa_output-maktx+0(1) = '"' .
 concatenate c_equal wa_output-maktx
 into v_maktx .
 else .
 concatenate c_equal c_colon wa_output-maktx c_colon
 into v_maktx .
 endif .
 if wa_output-name1+0(1) = '"' .
 concatenate c_equal wa_output-name1
 into v_name .
 else .
 concatenate c_equal c_colon wa_output-name1 c_colon
 into v_name .
 endif .
 v_name = wa_output-name1.
 v_lifnr = wa_output-lifnr.
 write wa_output-eindt to v_date1 DD/MM/YYYY.
 concatenate '="' wa_output-ebeln '/'
 wa_output-ebelp '"' into v_po .
 concatenate '="' wa_output-matnr '"' into v_matnr .
 concatenate c_equal c_colon wa_output-maktx c_colon
 into v_maktx .
 concatenate c_equal c_colon wa_output-dumng c_colon
 into v_qty1 .
 concatenate c_equal c_colon wa_output-eindt c_colon
 into v_date1 .
 concatenate c_equal c_colon wa_output-name1 c_colon
 into v_name .
 concatenate c_equal c_colon wa_output-eknam c_colon
 into v_eknam .
 concatenate c_equal c_colon wa_output-lifnr c_colon
 into v_lifnr .
 concatenate c_equal c_colon wa_mard-werks '/'
 wa_mard-lgort c_colon
 into v_lgort .
 concatenate '="' wa_output-lifnr '"' into v_lifnr .
condense:v_po,v_matnr, v_maktx, v_qty, v_date, v_name, v_eknam,v_lifnr .
 concatenate
 v_po v_matnr v_maktx v_qty
 v_date1 v_name v_eknam v_lifnr
 into i_download
 SEPARATED BY con_tab.
 concatenate con_cret i_download INTO i_download .
 append i_download .
endif.
clear : v_po,v_matnr, v_maktx, v_qty, v_date, v_name, v_eknam,v_lifnr .
endloop.
ENDFORM. " fill_report_csv
*& Form f_send_internet_mail
 text
--> p1 text
<-- p2 text
FORM f_send_internet_mail.
Variables
data: it_packing_list like sopcklsti1 occurs 0 with header line,
 it_contents like solisti1 occurs 0 with header line,
 it_receivers like somlreci1 occurs 0 with header line,
 it_attachment like solisti1 occurs 0 with header line,
 gd_cnt type i,
 gd_sent_all(1) type c,
 gd_doc_data like sodocchgi1,
 gd_error type sy-subrc.
data: it_message type standard table of SOLISTI1 initial size 0
 with header line.
data : found_receiver type c,
 v_title(80) type c,
 l_text(180) type c.
Fill the document data.
gd_doc_data-doc_size = 1.
Adds text to email text table
append 'Pls see attached open purchase order report.' to it_message.
append '' to it_message.
concatenate 'Note: This is system generated report'
 ', figures may subject to actual physical count.'
 into l_text separated by space.
append l_text to it_message.
Populate the subject/generic message attributes
CLEAR gd_doc_data.
READ TABLE i_download INDEX w_cnt.
gd_doc_data-doc_size =
 ( w_cnt - 1 ) * 255 + STRLEN( i_download ).
gd_doc_data-obj_langu = sy-langu.
gd_doc_data-obj_name = 'SAPRPT'.
if p_asdate is initial .
 concatenate p_title ' '
 sy-datum sy-uzeit into v_title separated by space.
else .
 concatenate p_title ' '
 p_bldat p_cputm into v_title separated by space.
endif .
gd_doc_data-obj_descr = v_title .
gd_doc_data-sensitivty = 'F'.
CLEAR t_attachment.
REFRESH t_attachment.
t_attachment[] = i_download[].
Describe the body of the message
clear it_packing_list.
refresh it_packing_list.
it_packing_list-transf_bin = space.
it_packing_list-head_start = 1.
it_packing_list-head_num = 0.
it_packing_list-body_start = 1.
describe table it_message lines it_packing_list-body_num.
it_packing_list-doc_type = 'RAW'.
append it_packing_list.
Create attachment notification
it_packing_list-transf_bin = 'X'.
it_packing_list-head_start = 1.
it_packing_list-head_num = 1.
it_packing_list-body_start = 1.
DESCRIBE TABLE t_attachment LINES it_packing_list-body_num.
it_packing_list-doc_type = 'XLS'.
it_packing_list-obj_descr = 'OPEN PURCHASE ORDER' .
it_packing_list-obj_name = 'PO.XLS' .
it_packing_list-doc_size = it_packing_list-body_num * 255.
APPEND it_packing_list.
assign SAP user smtp address from successful retrieval.
loop at p_email.
Add the recipients email address
 found_receiver = 'X' .
 it_receivers-receiver = p_email-low.
 it_receivers-rec_type = 'U'.
 it_receivers-com_type = 'INT'.
 it_receivers-notif_del = ''.
 it_receivers-notif_ndel = 'X'.
 append it_receivers .
endloop .
Add default recipient email when unable to locate purc group email
 if found_receiver is initial .
 it_receivers-receiver = p_email.
 it_receivers-rec_type = 'U'.
 it_receivers-com_type = 'INT'.
 it_receivers-notif_del = ''.
 it_receivers-notif_ndel = 'X'.
 append it_receivers.
 endif .
Call the FM to post the message to SAPMAIL
call function 'SO_NEW_DOCUMENT_ATT_SEND_API1'
 exporting
 document_data = gd_doc_data
 put_in_outbox = 'X'
 commit_work = 'X'
 importing
 sent_to_all = gd_sent_all
 tables
 packing_list = it_packing_list
 contents_bin = t_attachment
 contents_txt = it_message
 receivers = it_receivers
 exceptions
 too_many_receivers = 1
 document_not_sent = 2
 document_type_not_exist = 3
 operation_no_authorization = 4
 parameter_error = 5
 x_error = 6
 enqueue_error = 7
 others = 8.
Store function module return code
gd_error = sy-subrc.
Get it_receivers return code
loop at it_receivers.
endloop.
Instructs mail send program for SAPCONNECT to send email.
wait up to 2 seconds.
if gd_error eq 0.
 submit rsconn01 with mode = 'INT'
 with output = ' '
 and return.
endif.
ENDFORM. " f_send_internet_mail

Hi,
go through this link,
http://www.sapdevelopment.co.uk/reporting/email/emailhome.htm
you have some sample programs.
Regards,
Raghavendra

Report output via E-mail

Hi all,
i have a written a report where i need to send the report output to somebody via
E-mail.i am sending this report output via E-mail successfully.The receiver receives, my output in excel format.but this excel is not pivoted.
i want , the receiver should get my output in pivoted excel format.i.e my output data should be exactly fit in the excel sheet.
now the columns in excel sheet are overlapping.once i double clicked, the columns are getting separated.i do not want to double click.i want all the columns should come properly i.e excel field length should be adjusted as per the output field length.
i am giving my coding below.plz suggest how i can do the above thing .it's urgent.
any idea will be highly appreaciated.
Regards
if not p_email1 is initial.
 perform fill_report_csv.
 perform f_send_internet_mail.
endif.
FORM fill_report_csv.
 data : l_text(232) type c,
 v_matnr1(21) type c,
 v_matnr(21) type c,
 v_matkl(14) type c,
 v_maktx(45) type c,
 v_ttlstk(14) type c,
 v_verpr(14) type c,
 v_werks(14) type c,
 v_lgort(14) type c,
 v_char(10) type c,
 v_stks type p ,
 v_po(40) type c,
 v_qty(13) type c,
 v_qty1 type sy-datum,
 v_date(15) type c,
 v_date1(15) TYPE C,
 v_name(35) type c,
 v_eknam(18) type c,
 v_lifnr(15) type c,
 l_po(40) type c,
 v_matnr(20) type c,
 l_rate(11) type p decimals 5,
 l_flag type c.
concatenate c_equal c_colon 'PO no.' c_colon
 into v_po.
concatenate c_equal c_colon 'Material no.' c_colon
 into v_matnr.
concatenate c_equal c_colon 'Description.' c_colon
 into v_maktx.
concatenate c_equal c_colon 'Due Qty.' c_colon
 into v_qty.
concatenate c_equal c_colon 'Del Date.' c_colon
 into v_date.
concatenate c_equal c_colon 'Vendor.' c_colon
 into v_name.
concatenate c_equal c_colon 'Buyer.' c_colon
 into v_eknam.
concatenate c_equal c_colon 'Vendor Code.' c_colon
 into v_lifnr.
concatenate
 v_po v_matnr v_maktx v_qty
 v_date v_name v_eknam v_lifnr
 into i_download
 SEPARATED BY con_tab.
append i_download .
clear : v_po,v_matnr, v_maktx, v_qty, v_date, v_name, v_eknam,v_lifnr .
clear wa_output.
loop at i_output into wa_output.
 on change of wa_output-ebeln.
 clear v_lines.
 loop at i_eket into wa_eket
 where ebeln = wa_output-ebeln.
 v_lines = v_lines + 1.
 clear wa_eket.
 endloop.
**-- Checking of page break
 v_lines = sy-linno + v_lines .
 if 55 < v_lines .
 write:/0(161) sy-uline.
 new-page.
 endif.
clear v_lines.
 loop at i_eket into wa_eket
 where ebeln = wa_output-ebeln.
 v_lines = v_lines + 1.
 clear wa_eket.
 endloop.
*-- Calculating the due qty.
 wa_output-dumng = wa_output-menge - wa_output-wemng.
*-- Writing the Line items of the PO.
 read table i_ekpo into wa_ekpo
 with key ebeln = wa_output-ebeln
 ebelp = wa_output-ebelp.
 l_rate = wa_ekpo-netpr / wa_ekpo-peinh.
*-- Writing of PO detail
 if wa_output-dumng gt 0 .
 v_qty = wa_output-dumng.
 v_date1 = wa_output-eindt.
 v_maktx = wa_output-maktx.
 if wa_output-maktx+0(1) = '"' .
 concatenate c_equal wa_output-maktx
 into v_maktx .
 else .
 concatenate c_equal c_colon wa_output-maktx c_colon
 into v_maktx .
 endif .
 if wa_output-name1+0(1) = '"' .
 concatenate c_equal wa_output-name1
 into v_name .
 else .
 concatenate c_equal c_colon wa_output-name1 c_colon
 into v_name .
 endif .
 v_name = wa_output-name1.
 v_lifnr = wa_output-lifnr.
 write wa_output-eindt to v_date1 DD/MM/YYYY.
 concatenate '="' wa_output-ebeln '/'
 wa_output-ebelp '"' into v_po .
 concatenate '="' wa_output-matnr '"' into v_matnr .
 concatenate c_equal c_colon wa_output-maktx c_colon
 into v_maktx .
 concatenate c_equal c_colon wa_output-dumng c_colon
 into v_qty1 .
 concatenate c_equal c_colon wa_output-eindt c_colon
 into v_date1 .
 concatenate c_equal c_colon wa_output-name1 c_colon
 into v_name .
 concatenate c_equal c_colon wa_output-eknam c_colon
 into v_eknam .
 concatenate c_equal c_colon wa_output-lifnr c_colon
 into v_lifnr .
 concatenate c_equal c_colon wa_mard-werks '/'
 wa_mard-lgort c_colon
 into v_lgort .
 concatenate '="' wa_output-lifnr '"' into v_lifnr .
condense:v_po,v_matnr, v_maktx, v_qty, v_date, v_name, v_eknam,v_lifnr .
 concatenate
 v_po v_matnr v_maktx v_qty
 v_date1 v_name v_eknam v_lifnr
 into i_download
 SEPARATED BY con_tab.
 concatenate con_cret i_download INTO i_download .
 append i_download .
endif.
clear : v_po,v_matnr, v_maktx, v_qty, v_date, v_name, v_eknam,v_lifnr .
endloop.
ENDFORM. " fill_report_csv
*& Form f_send_internet_mail
 text
--> p1 text
<-- p2 text
FORM f_send_internet_mail.
Variables
data: it_packing_list like sopcklsti1 occurs 0 with header line,
 it_contents like solisti1 occurs 0 with header line,
 it_receivers like somlreci1 occurs 0 with header line,
 it_attachment like solisti1 occurs 0 with header line,
 gd_cnt type i,
 gd_sent_all(1) type c,
 gd_doc_data like sodocchgi1,
 gd_error type sy-subrc.
data: it_message type standard table of SOLISTI1 initial size 0
 with header line.
data : found_receiver type c,
 v_title(80) type c,
 l_text(180) type c.
Fill the document data.
gd_doc_data-doc_size = 1.
Adds text to email text table
append 'Pls see attached open purchase order report.' to it_message.
append '' to it_message.
concatenate 'Note: This is system generated report'
 ', figures may subject to actual physical count.'
 into l_text separated by space.
append l_text to it_message.
Populate the subject/generic message attributes
CLEAR gd_doc_data.
READ TABLE i_download INDEX w_cnt.
gd_doc_data-doc_size =
 ( w_cnt - 1 ) * 255 + STRLEN( i_download ).
gd_doc_data-obj_langu = sy-langu.
gd_doc_data-obj_name = 'SAPRPT'.
if p_asdate is initial .
 concatenate p_title ' '
 sy-datum sy-uzeit into v_title separated by space.
else .
 concatenate p_title ' '
 p_bldat p_cputm into v_title separated by space.
endif .
gd_doc_data-obj_descr = v_title .
gd_doc_data-sensitivty = 'F'.
CLEAR t_attachment.
REFRESH t_attachment.
t_attachment[] = i_download[].
Describe the body of the message
clear it_packing_list.
refresh it_packing_list.
it_packing_list-transf_bin = space.
it_packing_list-head_start = 1.
it_packing_list-head_num = 0.
it_packing_list-body_start = 1.
describe table it_message lines it_packing_list-body_num.
it_packing_list-doc_type = 'RAW'.
append it_packing_list.
Create attachment notification
it_packing_list-transf_bin = 'X'.
it_packing_list-head_start = 1.
it_packing_list-head_num = 1.
it_packing_list-body_start = 1.
DESCRIBE TABLE t_attachment LINES it_packing_list-body_num.
it_packing_list-doc_type = 'XLS'.
it_packing_list-obj_descr = 'OPEN PURCHASE ORDER' .
it_packing_list-obj_name = 'PO.XLS' .
it_packing_list-doc_size = it_packing_list-body_num * 255.
APPEND it_packing_list.
assign SAP user smtp address from successful retrieval.
loop at p_email.
Add the recipients email address
 found_receiver = 'X' .
 it_receivers-receiver = p_email-low.
 it_receivers-rec_type = 'U'.
 it_receivers-com_type = 'INT'.
 it_receivers-notif_del = ''.
 it_receivers-notif_ndel = 'X'.
 append it_receivers .
endloop .
Add default recipient email when unable to locate purc group email
 if found_receiver is initial .
 it_receivers-receiver = p_email.
 it_receivers-rec_type = 'U'.
 it_receivers-com_type = 'INT'.
 it_receivers-notif_del = ''.
 it_receivers-notif_ndel = 'X'.
 append it_receivers.
 endif .
Call the FM to post the message to SAPMAIL
call function 'SO_NEW_DOCUMENT_ATT_SEND_API1'
 exporting
 document_data = gd_doc_data
 put_in_outbox = 'X'
 commit_work = 'X'
 importing
 sent_to_all = gd_sent_all
 tables
 packing_list = it_packing_list
 contents_bin = t_attachment
 contents_txt = it_message
 receivers = it_receivers
 exceptions
 too_many_receivers = 1
 document_not_sent = 2
 document_type_not_exist = 3
 operation_no_authorization = 4
 parameter_error = 5
 x_error = 6
 enqueue_error = 7
 others = 8.
Store function module return code
gd_error = sy-subrc.
Get it_receivers return code
loop at it_receivers.
endloop.
Instructs mail send program for SAPCONNECT to send email.
wait up to 2 seconds.
if gd_error eq 0.
 submit rsconn01 with mode = 'INT'
 with output = ' '
 and return.
endif.
ENDFORM. " f_send_internet_mail

ans

Output via idoc/ale

Similar Messages

Maybe you are looking for