Outbound IDoc file question.. Please see..

Hi experts,
Is there a Function module to name the files which are outbound from SAP system eg ORDRSP or DESADV. I want the file to be saved in the server in a particular format...eg
Date_time_message type.txt.
What is the FM or user exit to be used for this. Then I need to probably give that name in WE21.
Thanks,
Charles.

Hi,
Have you looked the standard function modules available in transaction WE21 for file port (outbound file tab)?
If none of them meet your requirement then you can create custom one and assign to function moduled for file name entry (WE55). Once done, then you can use for your IDoc file port.
I would suggest to copy standard SAP which close to your requirement and modify accordingly.
Regards,
Ferry Lianto
Please reward points if helpful.

Similar Messages

IDoc XML - Flat File Question

Hello All,
I've gone through the 'How To Convert Between IDoc XML Structures and Flat Files in XI 3.0' guide. What I am having trouble wrapping my head around is the creation of the interface mapping, in particular the 'Target Message' interface. Obviously the 'Source Message' interface would be the incoming IDoc but what is the 'Target Message' interface that is used?
Looking forward to seeing the light,
Mike

Hi Mike,
your target message will be a XML structure which will be written to your output file.
The Structure will somewhat be of this type:
 <root>
 
 <Data/>
 
 </root>
And you need to configure the Receiver File Adapter to see your output, also you can use File Content Conversion to change the output to text.
For that please go through this weblog by Mr. Arpit Seth:
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
I hope it helps,
Thanks & Regards,
Varun Joshi

Convert custom outbound idoc to CSV file

Hi
I need to send generate a flat file that will be sent to a non SAP partner. A requirement is that the messages go via the IDOC system. This makes it possible to resend them if necessary.
So there are 2 stages
1) create IDOC. I have done this
2) read IDOC and convert to flat file
stage 1
=====
I have defined a custom IDOC, partner profile etc and developed a Function Module to create the outbound IDOCs The FM is triggered by a message in the NAST table. . This works OK.
So I now have custom outbound IDOCs in the DB with status 30 (ready for dispatch) (WE05).
Stage 2
======
Now I want to convert these custom IDOCs into simple flat files (CSV like).
How do I go about making this happen? I guess I need to develop another Function Module. But I dont know how to tie this FM into the system. My questions are:
How will the FM be triggered
what is the interface of the FM
will I need to configure a 2nd partner profile for stage 2 (which is fine)
Peter
Note1 - there is no EDI converter available so must solve this in ABAP
Note2 - I do not want to create the flat file at the same time as I create the IDOC. This would defeat the purpose of going via IDOCs

No, EDI is only one method of transferring data. There's no need for an EDI subsystem in this case.
To the OP, since it seems the you have decided that you must use IDOC processing in this case, I would go ahead and use a file port (or an XML port). You will drop an IDOC formatted flat file into the specified location (for each IDOC, based on your logical file definition). For you, this will merely be a temporary holding location. You can then use a simple program to read the file, re-format it, send it, then move the original file to a 'processed' location. Of course, you could also just throw away the generated files and read the IDOCs directly with the standard functions available and (re)generate/send the files as required.
It's often done this way with 3rd party EDI providers, where the company in question is required to use EDI by their customers but do not have the required systems in place.

What are the supported Macintosh Operating System versions for IBM SPSS Statistics 18,19 and 20? Question I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions 18, 19 and 20? Answer Please see

What are the supported Macintosh Operating System versions for IBM SPSS Statistics 18,19 and 20?
Question
I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions 18, 19 and 20?
Answer
Please see the list below:
- IBM SPSS Statistics 18 and 19 releases are supported on Apple Macintosh OS 10.5 (Leopard) and 10.6 (Snow Leopard) with Intel processor.
- IBM SPSS Statistics 20 release is supported on Apple Macintosh OS 10.6 (Snow Leopard) and 10.7 (Lion) with Intel processor.
- The IBM SPSS Statistics versions 18 and 19 are not supported on Mac OS 10.7 (Lion).
THIS MEANS THAT TO USE LION ONE FIRST HAS TO UPGRADE TO SPSS STATISTICS 20.

Whilst the 2012-02-15 edition of IBM's matrix does not mention Lion, a few users have noted that:
• 18.0 can be troublesome
• an updated version of 18.x should be better.
Related files
PASWStatistics_1 803_Mac_Patch.dmg and IBM SPSS Statistics 18.0.3.4 Hotfix Mac.zip are no longer available from the spss.com domain, and I could not find them in an IBM domain. If you download from unofficial sources, proceed with caution.
Related pages
In Apple Support Communities:
• will PASW (SPSS) 18 work with LION
• PASW statistics 18 crashes every time
• Java Virtual Machine & SPSS 18 with a question from me.
Elsewhere:
• SPSS on Lion « Decorator Pattern
• SPSS / PASW Mac Patch 18.0.3 and Graphing Fix | The Personal Website of Philip Fizur
• Patching PASW 18 (or SPSS 18) for Mac OS X (Leopard, Snow Leopard, Lion) to version 18.0.3.1
• and other sources, including one domain that I treat as reputable but I'll respectfully not share that link here.
At a glance, you might find that 18.0.3.4 is compatible with Lion.

Empty files created when outbound IDOC is wrttien to EDI

SAP is generating null ORDRSP and DESADV IDOC files. We've checked the individual IDOCs and they appear to be OK however the userdata/PO1/TLEDI/out directory clearly show the null value's. Has anyone encountered this kind of issue?

Hi all !
When is configuration XI , I have a error :
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/IS/LS//CREMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
Procedure
Please check the inbound partner profiles.
Execute function
I can't configuration it. Help me, plz !
Thanks !

Critical errors were found in setup. Please see setup log file for details.

What fixes this problem in IE? I have read a lot of forums with many replies saying they got by it, but they never explain how. One guy posted a link, but the link is dead now.
I need to know how to fix this problem. Only thing I can gather is its a Java issue, but my java is up to date. In fact I just reinstalled it make sure that it was updated.
With as many people having this issue I can't believe I have not found something from Adobe on this issue.
Regards,
Scott

I run the setup file and it does the checking system process... then goes into the actual install menu and not more than 10 seconds into that 2nd menu I get "critical errors were found in setup. Please see setup log file for details". That is all I can get out of the install.
The message window that I get the error in indicates windows Internet Explorer.
That is the my entire process. I have searched and found the log file and I have looked through it, but I am having a hard time finding the actual cause of the error. Out of shear frustration I removed all my adobe products and tried the install again and had the same exact problem. So I know there is something stopping me some where... just don't know what it could be.
Thanks,
Scott =

Exit Code: 16 Please see specific errors below for troubleshooting. For example, ERROR: DW039 ... Summary - 0 fatal error(s), 1 error(s) ERROR: DW039: Failed to load deployment File

Exit Code: 16
Please see specific errors below for troubleshooting. For example, ERROR: DW039 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 1 error(s)
ERROR: DW039: Failed to load deployment File

if this is related to the installation of an adobe product, Troubleshoot with install logs | CS5, CS5.5, CS6, CC

IDoc Outbound to File

Hi experts,
I have tried to output invoice IDoc to file (Obj. Name: INVOIC02). When I view INVOIC02 in WE30, I got the follow segments:
E1EDK01 - IDoc: Document header general data
However, I check with the IDoc file, I have E2EDK01005 instead of E1EDK01.
Any way to have my IDoc file to output E1EDK01 instead of E2EDK01005? Thanks.

Gundam,
E1EDK01005 is the standard segment name from SAP from 45B. You cannot change that. (unless you want to send out the IDOC's in version 30A which I'm sure is not your intension). It is also not recommended to manually change the segment names.
If you're converting to EDIFACT, then your EDI subsystem will do the mapping from IDOC format (flat file - as you said the port type is file) to EDIFACT (flat file in UN standards). Your EDI mapper will already have the EDIFACT standard loaded into his mapping software. You can simply go to WE60, give basic type (e.g. INVOIC02 etc), go to documentation, create DTD and then format 46 or unicode (depending on what your EDI subsystem is). Your EDI team will be able to use this DTD and use it as an input file in their map. This is fairly the standard process followed. Note: Many latest EDI systems come loaded with all the IDOC file definitions. So you do not even have to do anything.

Idoc outbound to file with multiple records

Hi Friends,
I want to export multiple materials into one flat file per ale (idoc).
I know I can create îdocs per "bd10" and download into file per WE19,
but only several files not many idocs in one file.
Can somebody help me with this requirement.
Actually I want to extract material data per Idoc and import it later per LSMW.
Many Thanks.
Jimbob

Your file port defintion (WE21) specifies the function module for creating the pathname (path + filename) for the IDOC file; most likely , it's EDI_PATH_CREATE_CLIENT_DOCNUM. You can replace this with your own Z-function or one of the other EDI_PATH_CREATE_ functions that will use the same path name over and over. You would not need to change the write mode, since it's already append mode by default in the system. Of course, you are correct, there are many other approaches available to get the data moved...

Is it possible to generate outbound idocs for FI invoices? How?

Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

Dear Gabriel
Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP. However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
thanks
G. Lakshmipathi

Query on User exit for outbound idoc

Hi ,
Can u all pls help me out to solve these queries
1. when we extend a new segment (at we31) and create a new idoc type(at we30), say,for DELVRY05 idoc type-what is the logic to be written inside the Exit(at Transaction code - CMOD -where a project is created and the exit is found for the enhancement) ,to view our extended segment -that needs to be appended (viewed below the existing segment)at we02?
2.Can we delete the outbound idoc generated with errors from development server?
3.How to recify the outbound idoc errors-like runtime,syntax,port unreachable errors(at the status record and data records listed inside we02 transaction code)?
4.How to check values populated at our extended segment inside we02-Transaction code.
say,the logic required inside the exit may be,
Select single ladel from eikp into wa_ladel where refnr = (inbound delivery)
In this,the ladel exists in eikp table as EIKP-LADEL field.
The main thing is- an inbound delivery is created at transaction code VL31N for which an outbound idoc(using an Exit )should be generated with few more validations for the fields like
i) ekpo-pstyp(corresponding IDOC segments are E1EDL26-PSTYV )
ii)ekko-lifnr and ekko-lichn(E1EDL24-LICHN )
Segment name-item(at transaction we63) Segment no.
iii) E1TXTP8-TDLINE => SCAC Code. 11
 E1TXTH8-TDID => Z001. 10
iv) E1TXTP8- TDLINE => Primary seal number. 13
 E1TXTH8-TDID => Z002. 12
v) E1TXTP8- TDLINE => Secondary seal number. 15
 E1TXTH8-TDID => Z003. 14
5.Can you help me out to know the logic by which we can validate few fields from different tables like eikp,ekpo and ekko inside our Exit (in the project created at CMOD transaction?
With Regards,
Srividya

Hi Swati Choudhary,
please ask your question in devlopment forum, please see its 2 yr old thread, and i don;t think Phileas Fogg still remember his stuffs.

About Orders05 outbound Idoc.

Hi,
I am using an outbound idoc of basic type Orders05 with an extension of the idoc header segment.This outbound idoc will get triggered once a PO is saved and sent through EDI.
I have to do an enhancement wherein I have to populate the mode of transport field(EXPVZ) and place of loading(LADEL) in the fields of the extended segment selecting them from EIKP depending upon the BELNR value in the header of the idoc(E1EDK01-BELNR).
I am unable to understand how do I populate the fields.
Could you please help me.
Thanks,
Sandeep.

HI,
see the below steps you will completely understand the processing outbound..
2.1 Outbound Interface
PROCESS DIAGRAM
Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
 Enter segment name and click on Create.
 The name of the segment type must start with Z1 , and have a maximum of eight characters.
 Enter description and enter the relevant field names and data elements.
 The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
 Save the segment and enter Person Responsible and Processing Person .
 Go to Edit and Set Release.
 Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
 Enter segment name (starting with Z), click on Basic Type and then Create.
 Create as new, enter Person Responsible and Processing Person and enter description.
 On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
 Complete relevant fields in the Maintain Attributes screen:
 From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
 The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
 The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
 Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
 When IDOC created return to initial screen. Go to Edit and Set Release.
 Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
 Display/Change and click on New Entries
 Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
 Display/Change and then click on New Entries.
 Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
 WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
 BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
 Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
 The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
 c_SEGMENT_type1.
 The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
 The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
 NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
 The ALE Layer handles the sending of the IDOC to the receiving system.
 Error Handling (see Step 7b).
 Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
 Declare a structure of type MCMAILOBJ for sending instructions.
 Enter values for the internal table based on structure MCMAILOBJ
 For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
 Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
 MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
 Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
 Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
 Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
 Enter your message type and execute.
 Status should be green, double click on one of the Idocs you have created to view its contents.
 If a problem has occurred click on Status which will give you a description of the error.
 Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
 Click on each individual segment and view the content to check that the correct data has been read.
 If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
rewards if useful
regards,
nazeer

Issue in Partner Profile config for Outbound IDOC

Hi Experts,
I have requirement like, When ever there will be any change in a Sales Order an Outbound IDOC will get triggered though a output type. This IDOC will save a file in the Application Server.
The Message Type i am using is ORDERS and the Basic Type is ORDERS05.
I have created a Partner Profile also a Receiver Port of type FILE.
I have Assigned Message type in Outbound Parameters.
I have assigned Receiver Port and Basic type under "Outbound Option".
I have Assigned Applications as 'V', Message type as 'Output Type' and Process Code under "Message Control".
When i am changing any Sales Order no IDOC is getting Triggered. I checked the Sales Order>Extras> Output> Header> Edit, the Output type is in Status RED with Message " No Partner Profiles (Message Control) Maintained".
Please guide me if i have missed any configs.
Help me solving this issue.
Thanks in Advance!
Priyabrata

Hi Priyabrata,
please try changing in your partner profile the application from V to V1. Another problem that's often causing the partner profile not to be found are the partner functions that are added automatically by SAP, but sometimes forgotten in the partner profile.
I don't have a SAP system at the moment, but as far as I remember the long text of the message indicates the partner profile parameters that SAP uses for the lookup.
If all of this doesn't help, I'd quickly debug this and see why SAP's not picking up the correct partner profile.
Cheers, harald

IDoc to XI u0096 Outbound IDoc

hi Experts,
Please let me know how to post IDOC to XI in R/3 Sender System?
Please help
Sourabh

Hi,
WE19 is the testing tool for the INBOUND and OUTBOUND Idocs,it will not post the data into XI.
What type of idoc ur using,To post the data into XI u have to trigger the IDOC in the transaction.
Suppoce u have to post the production order details then u have to go to CO02 TC code there u have to give the production order details and release the IDOC .
Before release the IDOC make sure u have done the ALE settings then the Data will be posted into XI.
Chech the ALE settings.
IDOC
http://msdn2.microsoft.com/en-us/library/ms942196.aspx
Idoc configuration Required~
in R/3
1) RFC destination pointing to XI
2) WE20 Partner Profile entries
in XI
1) RFC destination pointing to R/3
Go thru this -
configuration steps for receiving idoc in xi from r/3
Go thru these for Idoc to XI scenarios-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

Regarding outbound idoc into xml conversion

Hello everyone
can anyone let me kno all the procedure to make our idoc outbound and convert it into XML file, is there any standard program or any other method if i am using we21 then what thing i have to do. is it neccesary for us to go to tc we60 and change schema of our structure or not, i don't want to use XI, please tell me whole procedure if possible, waiting for your reply.
plz reply me.
Thanks & Regards
vimarsh b
Edited by: vimarsh b on Jan 8, 2008 5:58 AM

hai,
check this.
Outbound Interface
PROCESS DIAGRAM for Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
? The name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
? The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
c_SEGMENT_type1.
The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
The ALE Layer handles the sending of the IDOC to the receiving system.
Error Handling (see Step 7b).
Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
Declare a structure of type MCMAILOBJ for sending instructions.
Enter values for the internal table based on structure MCMAILOBJ
For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
Enter your message type and execute.
Status should be green, double click on one of the Idocs you have created to view its contents.
If a problem has occurred click on Status which will give you a description of the error.
Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
Click on each individual segment and view the content to check that the correct data has been read.
If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
also gothroughthe links,
http://www.theobald-software.com/download/ERPConnect/ERPConnectDevGuide_EN.pdf.
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
With regards,
Sowjanya.B.

Outbound IDoc file question.. Please see..

Similar Messages

Maybe you are looking for