Trigerring idoc in idoc2file scenario

Hi
how the idoc is triggered in scenario idoc2file,in which idoc is on sender side and file on reciever side.
regards
prasad

Hi,
Once you configured the ALE settings, ask your functional people to generate the idoc. then goto we02 take the IDOC number fom there and paste it in WE19 ( IDOC Test Tool)
And then u can send the IDOC from R/3 to XI in this way
ALE Settings
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Reposting IDocs instead of Recreating - For Testing
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
IDOCXI-File Scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
REgards
Seshagiri

Similar Messages

Issues in IDOC to File scenario using bussiness service

Hi Team
I found a blog which explains about the IDOC to FILE scenario by using bussinss services. I followed the steps and finally i am getting a error message while posting an idoc in we19 (ie IDOC 09878 was saved but cannot or should not be sent). The setting which have done on SAP side are as below
SAP SIDE CONFIGURATIONS
1. Created RFC destination : RFC_XI_SYSTEM
2. Created port : PORT_TEST
3. created logical system: IDOC2FILE
4. created partner profiles: IDOC2FILE
XI side configurations
1. Created RFC destination: RFC_SAP_SYSTEM
2. Created port : by using IDX1 t-code
DOUBT: here it is asking for PORT, CLIENT,Description and RFC destination, please let me know what values i need to put here, please find the SAP and XI system details below and suggest accordingly.
3. metadata: by using idx2.
DOUBT: here it is asking for IDOC type and source port, i can give the idoc name but i am not getting what i need to give to source prort field, please check and let me know, please find the SAP and XI system details below and suggest accordingly.
SAP system details
Client: 800
User name: sapuser
system id: DEV
system number:10
XI system details
Client:100
username:xisuper
system id: SXI
system numebr: 00
I request you to please check and help to successfullly completion of this scenario. I request you to please provide me the screen shots of the pre-requiste settings and suggest me the steps to debug the scenario.
Thanks in advance.
Raju

To complete your scenario successfully with better understanding of Idoc adapter
read http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm.
for troubleshooting refer http://help.sap.com/saphelp_nw70/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

IDoc to File Scenario Error ( IS - Retail )

Hi all ,
I was trying scenario IDoc (SAP ECC 6.0) (IS-Retail) to File scenario .
When i trigerred IDoc from ECC system , it's showing sent successfully to external system or program.
But the problem is it's not coming inside XI sxmb_moni .
I have checked the ALE Configuration and SLD configuration .
Everything is fine.
When i run the TCODE WE05 for IDocs List in XI , it's getting stucked there and the Error showing is
"IDoc: 0000000000000028 Status: IDoc with errors added
External segment name E2WBB01003 cannot be interpreted "
Even i tried with other IDoc WPDWGR it is showing the same error
"IDoc: 0000000000000029 Status: IDoc with errors added
External segment name E2WPW01 cannot be interpreted"

Hi Ashwin,
Please check :
1.The SAP system from which you want to import the IDocs contains function modules for calling metadata.
2.You can import IDocs from SAP Release 4.0 and higher.Support Packages Required for IDoc Imports:
Release    Minimum Support Package Requirement
40B                   SAPKH40B48
45B                   SAPKH45B26
46A                   SAPKB46A20
46B                   SAPKB46B12
46C                   SAPKB46C05
3.check for the authorizations required to import.
Also see SAP Notes 677732 (authorizations), 672745 (missing function modules), 212011 (access to IDoc metadata), and 718320.
check http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
*Pls: Reward points if helpful*
Regards,
Jyoti

How to test IDOC2FILE Scenario

Hi All,
Now i am working on IDOC2FILE scenario. I have done all ALE settings in R/3 side with RFC destination, port, Partner profile.
At XI side i created RFC destination, Port and Partner profile also.
And i pushed the idoc from R/3. I got the status messages like
"IDoc: 0000000000001018 Status: Data passed to port OK" and "IDoc sent to SAP system or external program".
But in XI, i got the following messages:
"IDoc: 0000000000005005 Status: Application document not posted" and
"Function module not allowed: APPL_IDOC_INPUTI".
All my design time and configuration time objects are done and activated.
Here i am using the business service for sender system. sender is R/3 system.
Anybody, came across this problem, could you please revert back to me with solution. I want step-by-step testing procedure.
Please getback to me with proper solution asap.
Thanks & Regards,
Nagarjuna.

Hi Sarvesh,
Thanks a lot. I already triggered the idoc in we19 and please go through the following once again:
I have done all ALE settings in R/3 side with RFC destination, port, Partner profile.
At XI side i created RFC destination, Port and Partner profile also.
And i pushed the idoc from R/3. I got the status messages like
"IDoc: 0000000000001018 Status: Data passed to port OK" and "IDoc sent to SAP system or external program".
But in XI, i got the following messages:
"IDoc: 0000000000005005 Status: Application document not posted" and
"Function module not allowed: APPL_IDOC_INPUTI".
All my design time and configuration time objects are done and activated.
Here i am using the business service for sender system. sender is R/3 system.
Anybody, came across this problem, could you please revert back to me with solution. I want step-by-step testing procedure.
Please getback to me with proper solution asap.
Thanks & Regards,
Nagarjuna.

IDOC2FILE scenario

Hi All,
I am going to develop idoc2file scenario in XI. Any body have the full documentation with step-by-step process(including R/3 settings & XI settings), Please send me ASAP.
I am very thankful to you in advance.
Thanks & Regards,
Nagarjuna.

Hi nagarjuna,
ALE configuration
Steps to do ALE Configuration with respect to IDOC:
Configuration in R/3:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using we21 and refer the port to the created RFC dest in above Step.
3. Create a Logical System using Transaction BD54.
4. Create a partner profile using transaction WE20.
Also need to configure in XI:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using Transaction IDX1 and refer the port to the created RFC dest in above Step.
3. The port has to be displayed in the IDX2 transaction and we should be able to view the idocs which we imported through integration repository otherwise we have to manually import the idocs from IDX2 using the port created above
Please refer to these blogs:
Complete process for Idoc to file scenario:
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
incase you are struck with any issues while creating the scenario refer to this blog;
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Hope this will help you:)
reward points if helpful
regards,
Nithiyanandam

Problem in TRFC queue (SM58) - IDOC2FILE scenario

Hi,
I am executing IDOC2file scenario. In the transaction we19, i have successfully posted the IDOC to external system (XI).
But the iDOC is still in TRFC queue. (SM58 or BD87).
Recipient details
Port : RFC in We21.
Partner No. : XI logical name.
Partner Type: Logical system.
Sender details
Port : SAPBIW
(This is the confusing part, I was told that first three letters should be SAP and next three should be SID of the SAP system).
Is this mandatory. But my TRFC (we21 in BW) didn't have any such port, so i created one.
Partner No. : BIW logical name.
Partner Type: Logical system.
I am getting this error in SM58
Transaction IDX1: Port SAPBIW, client 001, RFC dest contains error.
Now i want to know what is the problem because of which IDOC is not being to pushed to XI

Hi,
go to sm58 and release or delete that queue, next time idoc will not stuck in the queue.
<<<Port : SAPBIW
(This is the confusing part, I was told that first three letters should be SAP and next three should be SID of the SAP system)Is this mandatory
It is not mandatory, you can leave this option blank.
Thanks

ALE settings for IDOC2FILE Scenario

Hi All,
I have the requirement to work on IDOC2FILE scenario. i am not able to do the ALE settings well in both R/3 side and XI side. Anybody have the full documentation with step-by-step analysis, please send me ASAP. Please help me in this regarding.
I am very thankful to you all in advance.
Regards,
Nag.

Hi Nagarjuna kumar ,
The following websites give u step-by-step solution for ALE settings for IDOC2FILE Scenario:
A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
cheers!
gyanaraj
****Pls reward points if u find this helpful

Regarding IDOC 3 File scenario

Hi This i Uday, please help me on IDOC2FILE scenario. i have done all the design and configuration part in XI.
for ALE settings
In R3 System
I have created alogical system named ls_uday,by using TC BD54.
and then i assigned this logical system for my R3 client 800.
and then i created my rf connection using transaction code SM59 named ls_uday, in that
i have given in technical setting i have given the target host as XI ip number and sys number
and logon settings as my xi usr name and passwd. and then i have created the port using tc we21 ls_uday.
and then created partner profile using tc we20 and then added the respective idoc as outbound.
In XI i also created same
bd54 ls-day
sm59 ls_day
idx1 ls_day
idx2 ls_day.
whre i have to do model view. please help me on this issue as early as possible.
don't send me any screen shots explain in textual format.

Hi,
go to BD64 distribution model and create a model view and goto ENVIRONMENT Tab..
Steps
SAP 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 (IDX1)
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)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP 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 (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.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
idoc to idoc
regards,
Kishore

Idoc-xi-file scenario. how to display file in html format

I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
Kumar

Hi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar

In idoc to file scenario, if XI system is down where do idocs pile up?

In idoc to file scenario, if XI system is down where do idocs pile up (get stuck)
what tcode can I use to reprocess it?

Sender System ,Check BD87 .. you will see alll the IDOCs in Yellow state ..
You can reprocess all the IDOCs in go from there .. if only they are in yellow state ...
regards
PS

FIle Content Conversion Problem in IDOC-XI-File Scenario

Dear All,
I am doing IDOC-XI-FILE scenario.
I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like %store_code%_%current_date%_sitemaster.xml , I have completed the dynamic generation successfully .
Now there is slight change in the requirement ,we have to suppress the current_date node of the xml content . i have tried to suppress the current_date using these DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut , But I am unable to suppress it Can some body provide me the details on this .
The output xml version generated by Reciever file adapter is as below :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
</ns0:MT_SITE_MASTER>
Plz provide me the code I have to write in the file content conversion .
Thanks in advance
Regards
Prabhat

If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier. Then use the Suppress Logic for the Current Date.
So it will look like this-
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
<CURR_DATE>
<CURRENT_DATE>20051105</CURRENT_DATE>
</CURR_DATE>
</ns0:MT_SITE_MASTER>
So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
CURR_DATE.fieldFixedLengths - 0
CURR_DATE.fixedLengthTooShortHanling - Cut
And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
Hope this solves ur problem.
Regards,
Moorthy

Error/Doubts in Idoc-XI-File scenario

Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.Jain

Hi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps .

Pass system ack of JDBC adapter to ERP in IDoc - XI - JDBC scenario

Dear all,
i have an IDoc -> XI -> JDBC scenario (without using ccBPM). In the standard way the ERP system, sending the IDoc waits for an application acknowledgement. However the JDBC adapter is only capeable to send system acknowledgements.
Is there a way to pass these acknowledgements to the IDoc status record?
In help.sap.com (http://help.sap.com/saphelp_nwpi71/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm) under "IDoc Processing with the IDoc Adapter " there is a table that maps XI system/applic acknowledgement to IDoc status. So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
Can anyone tell, if this is really working? What if I deactivate the acknowledgement request in the NOALE programm?
In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
Many thanks and best regards
Florian

Is there a way to pass these acknowledgements to the IDoc status record?
Without BPM, No.
So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
The ack referred here is related to idoc status whether it is properly reached till XI or not and not related to the JDBC ack.
What if I deactivate the acknowledgement request in the NOALE programm?
Then u won't have any ALEAUD message at sender R3.
In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
No
Regards,
Prateek

Integration server as logical system in IDoc to file scenario

Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.

Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra.

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

Trigerring idoc in idoc2file scenario

Similar Messages

Maybe you are looking for