Abt idoc

hi all,
my query is on idoc interface,i have already devoloed idoc from this i have to do outbound interface.
i have z_tp_idocread function module which gives the idoc data i have to populate this data first.so tell me the code for this.
after we get the data .i have basic type zrmd_a07 for custom fields.and hrmd_a07 for normal fields.so suppose in 'header field' is record type of type char and in 'trailer field' i have 'record count' of type char,and in body i have to retrieve emp_last and the idoc field for this is e1p0002-name2.
so like this i have to map in header trailer and body format.
so plz try to give me code for this its very urgent.
plzz plz plz i want example code for this u can give with some fields.

can u give bit more explanation?

Similar Messages

Requirements for IDOC

Hi friends,
Could you please tell me the details required for doign a IDOC scenario.
I want the details seperately when IDOC is a sender and also when IDOC is a receiver.
Note: High reward points for the reply

HI
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Idoc creation
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
You can get the all description from below tcodes
WE60-> Documentation for IDoc types
WE09-> Search for IDocs by Content
BD87-> Status Monitor for ALE Messages
WE63 -- information about Standard IDOC in R/3
WE64 - Details about process codes
WE82, WE30, WE31 -- IDOC Types.
SAP R/3
R/3 to XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
XI to R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Details ABT IDOC??????
1)Use WE60 transaction.
2)you need list of basic type idocs then use t.code WE60.
To display IDOC list in particular time intervel use we02 or we05.
where u can find the outbound and inbound processing idoc's.
use t.code 'wedi' to get more information on idoc's.
3)You can use the WE60 for Idoc Documentation
& we can use WE30 for Idocs list
Refer the below links for furtehr assistance
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
cheers

IDOCs in CM

Hello
I am implementing Compensation Management in 4.7 vs 2 which would allow for merit increases to be given through MSS.With that workflow in mind, how would IDOC's come into picture for the entire project. I dont have much idea abt IDOC's . As of now, PY is done thru ADP and they use IDOC's for that here.
Please do suggest how do I move fwd
Thanks

I don't see the relevance of IDocs in the context of ECM & MSS. The merit increases will initially be stored in infotype 0759. But once it is approved, it will be distributed across 0008,0015 & 0267 depending on the type of merit increase ie salary hike, lumpsum bonus etc.. These records will be passed onto ADP just like any other payroll data..
~Suresh

IDOCs for CRM

Hi,
I've read about CRM Middleware, ALE/EDI and the usage of IDOCs for communication between SAP CRM and Non SAP System.
I need to see the existing IDOCs that can be used for CRM.
For example I need an IDOC for a Service Order... this is just an example, how can I search them?
Thanx in advanced.
By the way, if you have any doc about CRM Middleware and a 3rd party system communication I will be very greatful if you can send it to urjose/at/yahoo(dot)com

Hi
r u willing to know abt bdoc in CRM
toknow abt idoc check this
http://help.sap.com/saphelp_nw04/helpdata/en/c2/090b374e4e7c64e10000009b38f839/frameset.htm
for middleware documents take building blocks and follow which will help u a lot
follow the Building Blocks C71 CRM Connectvity
B09: CRM Customizing Replication
C03: CRM Master and Transaction Data Replication
to download the building block click
http://help.sap.com/bp_crmv152/CRM_DE/HTML/index.htm
go to technical Information
go to building block library
Reward points if helpful
REgards
Manohar

Idoc recieving

Could someone solve my problem plz....
I have an Idoc which is being transferred from R/3 to XI and then a different R/3.
At idx5 the idoc is seen to be successfully arrived at XI but it is not showing me that wheather it has gone to the desired reciever R/3 or not.
But at sxmb_moni it shows that there is alink between XI and desired reciever and that the Idoc has not been transferred.
So I want to ask that if the Idoc is being shown not delivered to reciever at sxmb_moni but at idx5 it is not even telling me wheather there is a link between XI and desired R/3 or not.....So does this means that there is a successful link between XI and desired R/3 reciever.Forget abt Idoc transfer or not??
Also plz tell that if there is a link being shown between XI and r/3 but it shows a red flag at sxmb_moni, can this be possible that the settings of sm59,we 21 etc... have not been done properly pointing to XI
Plz answer my above2 Questns.
Thanx

Hi,
But at sxmb_moni it shows that there is alink between XI and desired reciever and that the Idoc has not been transferred.
So I want to ask that if the Idoc is being shown not delivered to reciever at sxmb_moni but at idx5 it is not even telling me wheather there is a link between XI and desired R/3 or not.....So does this means that there is a successful link between XI and desired R/3 reciever.Forget abt Idoc transfer or not??
A) When u see the message in SXMB_MONI with sucessful flag then u consider that ur scenario is completed succesfully.
1) Now in order to check the IDOC is reached R3 system or not first check the Reciever information in SXMB_MONI.Form that receiver information u will come to know it is send to which system this information is as per the configuration which u have done in ID.
2) Check the IDOC receiver communication channel and the details which u have put.
3) Go to receiver R3 system and run WE02 transaction and check the IDOC status.
Also plz tell that if there is a link being shown between XI and r/3 but it shows a red flag at sxmb_moni, can this be possible that the settings of sm59,we 21 etc... have not been done properly pointing to XI
A) there could be many reasons
Check the below troubleshooting guide which has error descriptions and solution also.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Thnx
Chirag

Idoc Testing! Need help!

Hi!
 (Please give answers specific to my question & pls read below)
 i want to test idoc outbound as well as inbound.
First Consider inbound,
 I ve read previous posted threads it was mentioned goto>we19> give idoc no
I want to know what is idoc no how we get idoc no for the idoc.

Then i know the steps...
Now Outbound,
How to test outbound idoc -- i want to know how my posting program has correctly generated idoc to ale layer.
I want this in complete detail.
 Thanks!
 Rahul.

Hi Rahul,
idoc structure
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html
What is Idoc?
I give overview of IDoc terminology and how IDocs work in an enterprise will clarify the process
SAPs presence in the IT world is justified by a central premise: It turns a companys many individual systems into one, big supersystem. More than a linking together of applications, SAPs implementation causes a redirection of the flow of information through a company and its partner companies that enhances the potential of its business functions.
This flow of information is enabled by a core element in SAP technology: the Intermediate Document, or IDoc. Technically, the IDoc is an example of Electronic Data Interchange (EDI). Unlike conventional EDI, IDocs are not based on a descriptive language.
The IDoc concept borrows the best features of EDI and combines them with the best features of conventional transaction file formats. The result is a lean data transport mechanism that is the engine of SAP data flow, tying together applications, databases, companies, and networks. Here is a look at the makeup of IDocs within the application architecture.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI (see Figure A).
Figure A
IDOC number Sender Receiver Port Message type IDoc type
1234567890 R3NYC R3LA FILE INVOICES INVOICE01
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records (see Figure B) are used to record these errors and the date/time of their occurrence.
Figure B
(Display Status Record)
IDoc number 0000000000123456
Direction 1 Outbound
Status information
 38 IDoc archived
(additional descriptive text)
Log time
 Date 6-30-02
 Time 14:35:21
Portion of IDoc status display
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system (see Figure C).
Figure C
CONTROL RECORD
DATA RECORD - CUST PROFILE LOC #1
DATA RECORD - CUST PROFILE LOC #2
DATA RECORD - CUST PROFILE LOC #3
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #1
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #2
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #3
STATUS RECORD
STATUS RECORD
STATUS RECORD
Records in a multiple-message IDoc
Final thought
There is no mastering SAP without mastering its workhorse, the IDoc. ERP environments utilizing SAP and similar platforms are made necessary in the first place by the increasing demands of ever more integrated business relationships. IDoc technology addresses this trend with a simple but powerful design philosophy: Data is no longer something to be stored; its something to be moved.
And
These links give u complete details abt idocs testing
Test Tool
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b80f643d711d1893e0000e8323c4f/content.htm
Status Monitor for ALE Messages
http://help.sap.com/saphelp_nw04/helpdata/en/d4/0d67e4d85511d2a6080060087832f8/content.htm
Regards ,
Kumar.

How to create inbound PO using EDI & IDOC???

hi friends,
I dont know abt IDOCs and EDI. Can any body give solution how to create po by using in bound process. plz give step by step. because I ever worked on EDI and IDOCs.

Hi there,
Please have a look at the following link.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
Hope this helps,
Kind Regards,
Matthew

Abt ale and idocs

hi gurus
    how can i specify the mode port packet size and all these things in partner profile.
with thanks
aru.

hi,
for idocs partner profiles, ports are necessary. follow the steps that may help u.
1. create and assign logical systems. [SALE]
2. create and assign RFC destinations for sender n receiver [SM59]
3. create partner profiles for sender n receiver [WE20]
       i. before partner profiles u have to create ports for sender n receiver [WE21]
       ii. after creation of partner profiles give inbound and outbound parameters for sender n receiver.
out bound parameters: give port no, message type, logical system.
inbound parameters: give process code,message type......... n save
if u want to have a custom idoc then
     i. define n create a message type [We81, WE82 ].
     ii. define n create segments [WE31, WE32 ]
4. create a model view in [BD64] by clicking on display/change button and clicking on create model view button.
5. assign message type to model view.
6. create a filter if u require.
7. goto environment -> generate partner profiles -> give receiver logical system name -> continue.
then u ll get the status.
if useful reward some points.
with regards,
Suresh.A

Query abt Inbound IDOC.

Hi,
I am creating a custom FM for processing Inbound IDOC.
I have configured my Inbound IDOC in cutomer profile and the Process code, which is pointing to the custom FM.
In tables section of my FM, I am receiving EDIDC n EDIDD type tables.
Now If I fire my IDOC, Does the IDOC information is transfered automatically to my FM.
Cheers,
Sam

It depends on the Idoc mapping in the partner profiles of WE20.
//where I have to select the inbound FM, But I don't find the entry for my FM.
Do you have an entry on that particular Fm and message type in tocde We57?
if yes then proceed as
Final check once this is over in Tcode WE57
Open tcode WE19 and give the message type of ur idoc in same and execute .
This will open your idoc . Populate it with control record details and data details .
and now click inbound function module .
this will pop up a window asking for Function module and then process the same in Debugging mode and execute it .
This is a replica of how the Fm is called manually.
Since in WE57 the mapping is done for the Message type and Fm it will pick the Fm .
regards,
vijay.

Terms of payment in IDoc E1EDK18 have been transferred: Check data

hi Firends,
In my scenario , i have to convert incoming purchase order to sales order in my system . I am able to get message from partner and idoc is created to the message bt it contains error,
tht is Terms of payment in IDoc E1EDK18 have been transferred: Check data
related to this I had gone through note 388120 - Transfer of conditions and terms of payment.
which says that i have to maintain tht entry in SMME tcode.
My confusion here is, while I tested same scenario in development , and quality server , it was not giving any such error bt in prod system i m gettin this error.
Also if some one knows more details abt this note ,let me know.
Thanks ,
Brijesh Soni

Hi Brijesh,
you are more likely to get a response for this query if you create a thread in the SD forum.
Regards
Kenny Scott
XI/PI SDN Forum Moderator

Creation of idoc

Hi,
im tryin to sent idoc from one sap server to another
what i should do in partner profiles and port definition and rfc destination
what should be the partner number in partner profiles
i have created idoc type and segment type after can anyone tel me abt partner profile and also abt outbound process
Thanks

Hi,
For Port Creation, Go to TCode WE21>if both the servers are R/3 then cclick on Transactional RFC then press F7> click radio button "Own Port Name"> tehn give description and give the "RFC destination" which u given in "SM59".
Partner Number is the "Receiving System" which u have assigned thro T Code SCC4 and BD54.
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
Regards,
Suresh
Message was edited by:
SureshKumar Ramamoorthy
null

BPM - IDoc to SOAP problem (Unable to convert sender service)

Hi,
I have a BPM scenario where I'm sending an Idoc from r/3 to XI to SOAP. As part of my scenario I'm sending an acknowledgment (ALEAUD) back to R/3.
I'm getting Unable to convert sender service IP_BPEL_INBOUND_ORDER to an ALE logical system on the Ack back.
So I usually know what to do when I get this, I do the SLD settings on the r/3 service and I'm OK. But in this case, it's asking for those ALE settings on the Integration Process?
I tried adding a logical system on it but now I'm getting the error that this is already used by the r/3 service. So I'm not to sure what to do next???
Rgds,
Yves

Ok do one thing, in you mapping take one field at target side (may be u can create one or use which is not been used yet) just map the standard function called Sender to this field in target.
Now in Intergration Directory when you do the header mapping by using F4 do not map the business systems this time, just press the button "Etended Path" (m not sure abt the exact name of this button) not use the X-Path here and select that target field which you mapped with Sender function in mapping.
How To Handle Acknowledgments for IDoc
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
I hope this will solve your problem.
Regards,
Sarvesh

Idoc-xi-jms scenario

Hi
I want sender service name in the receiver payload header. How should we go abt ? I am talking abt the scenario like idoc-xi-jms.
thanks
kumar

have a look at the following
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/frameset.htm
Thanx
Aamir

IDOC Flat File-- XI-- IDOC

Hi,
I have a requirement wherein we have to read the IDOC flat file and post it as IDOC to SAP using XI. I understand we have to use the Flat File Sender adapter and the IDOC Receiver Adapter. On the Sender Side we have to define the Content Conversion to convert the IDOC Flat File to IDOC XML. Writing File Content Conversion for the IDOC Flat File would be very tedious because of the number of fields and fixed structure of the flat file.
I have don through the following guide Section 3.2 where it talks abt converting IDOC to IDOC XML using reportRSEINB00.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20convert%20between%20idoc%20and%20xml%20in%20xi%203.0.pdf
I am not clear how to invoke this report in the Flat File Sender adapter. Also is there any other approach.
Thanks
Rajeev Gupta

Hi Rajeev
You have a flatfile at the sender side so you dnt have any feasiable option to do other than FCC....FCC is not a tediuos one...if you can provide the strucutrre we will help you out...
Check out you have a fixedlength file or piple separated one....
In the functional design how many fields re present and buil the DT,MT MI accoprdingly.....
you have to just use some conecnt conversion parameters that's it...
item.fieldSeparator
item.endSeparator
item.fieldNames
here item is your recordset name
let us know your strucutre
regards
Nisar

Idoc PEXR2002 is not getting tiggered frm T-Code F110

Hi All,
I need to trigger the Idoc PEXR2002, from the T-Code F110. The payment process is successfull, but the Idoc is not getting triggered. I am not able to find the exact reason for that.
We have a tab with name printout/data medium and it has got the following programs in it 1. RFFOAVIS 2. RFFOEDI1 3. RFFOUS_C. Is there any thing I need to do with these??
Please help me..
Thanks
Suma.

Hi suma,
Now i have requirement to generate payment file
whan we execute F110 using enhancement IDOC(EDI) . I want to know ,by which method i can trigger
IDOC ( by message control ,work flow or standard program) .if it is message control what is process
code for this.
I think u have worked on this .if u have information abt this plz forward me .
Thanks & regards,
Balu.

Abt idoc

Similar Messages

Maybe you are looking for