Need an alert to be sent after succesful completion idoc to file scenario.

Hi ,
we have an idoc to file scenario, the user wants a email confirmation after the file is generated, can any body help how i can trigger an alert once file is generated by xi(in a idoc to file scenario).
regards
sandeep

Hi Sandeep,
we have an idoc to file scenario, the user wants a email confirmation after the file is generated, can any body help how i can trigger an alert once file is generated by xi(in a idoc to file scenario).
Well, you can generate an email after your file has been sent (use BPM for this).
But I believe your Client wants a confirmation of file delivery through email, which might be a problem. By using the above step, you will be able to send the email after file is sent, but it won't confirm whether the file has been successfully delivered.
You need a synch message which file won't be supporting. So, the other way is to ask your Client if it is possible for them to send an acknowledgment to PI after receiving the file, and then you can trigger the email.
Unfortunately, there is no straight way out for your problem.
Hope this helps.
Regards,
Neetesh

Similar Messages

Alerts when the acknowledgement fails in IDOC to File Scenario

Hi All,
could you let me know how to handle Alerts for Idoc to File scenario.
My Scenario uses BPM as well.
Thanks,
Srini

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Do we need a sender channel for IDOC to file scenario.

Hi,
Do we need a sender channel in IDOC to FILE scenario.
Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
What is the reason for this?
Regards,
Younus

Younus,
to add more...
From WAS(Web Application Server) 6.20 and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
And it has got ABAP and JAVA engine in it.
It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.

The SAP Web AS 6.10 did not have a Java engine.
and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
Hope i cleared ur point...
Cheers,
Raghavesh
Message was edited by:
Raghavesh Reddy

Why we dont need sender agreement and comm channel in IDOC to file scenario

Hi,
there are 2 queries:
first query :
Scenario is "Idoc to file transfer"
why we dont need sender agreement and communication channel for IDOC to file ,while we do need
both of these for "File to RFC "
Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
Then why For "IDOC to file" we dont need that.
Second query:
Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
and getting data from RFC back to File2.
Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
Regards,
Mayank
Edited by: mayank verdia on Jan 13, 2009 11:49 AM
Edited by: mayank verdia on Jan 13, 2009 11:50 AM

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

IDOC to File Scenario - Configuration steps need to be done in R3 and XI

Hi Experts,
I am working with IDoc to File scenario. Can someone please explain, what are the steps or configuration things need to be done in R3 and as well as in XI too.
Thanks in advance.
Regards,
Sree

Hi Sree,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this answers your query.
Regards,
Abhy Thomas

Which all configurations you need to do in R/3 for an Idoc to file scenario

which all configurations you need to do in R/3 for an Idoc to file scenario?
Rgds
Ruchitha

Hi ruchitha thakur ,
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
Integration Builder
Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
The following web-sites give u step-by-step solution to configure R/3 :
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
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
Step by Step Procedure of IDOC to File Scenario using BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
cheers!
gyanaraj
****Pls reward points if u find this useful

Alerts-Idoc to File Scenario using BPM

Dear all,
At the sender side,I am sending 2 Idoc's orders03,orders04 Idocs I am Merging in to single at my mapping level and sending to the respective receivers.
When even some error occurs at system level or application level,an alert must be sent to the respective valid receipents.
My question is,when creating the Alert Rule how to use the interfaces(orders03,04) (here I have multiple senders).
Is Alert rule required in BPM scenario's?if not let me know how alerts would be triggered for bpm scenarios.
Thanks,
Srini

Hi,
Let me see if I had you requirement correct.
When the Idoc is sent from R3, sender partner type is LS and Receiver Partner Type is LI.
If yes,
1. Create a Party in ID.
2. The Agency , Scheme and Identifier will have values,
Agency --> Receiver Business System name or Business Service Name to be used for File.
Scheme --> ALE#LI
Identiier --> Value of the RCVPRN field in the idoc control Record. Basically the Receiver Partner Name.
All the Configuration In ID will use this Party as the Receiver Party and the corresponding Service asthe Receiver service.
No need for a sender party as sender partner is LS.
Regards
Bhavesh

Help needed in Idoc To File Scenario

Hi Experts,
My scenario is Idoc to File.
Here my job is to convert the purchase order idoc into xml file.
In this there are three conditions.
                   converting the standard PO into xml file
(ii)                 converting the PO with serial number into xml file
(iii)                converting the PO using serial number with subcontracting into xml file
so what I feel is I need to create one scenario and based on the condition that particular PO will convert into xml file.
Conditions:
                   if no condition is specified then it is standard PO first case
(ii)                 if field tdline ne space then it is PO with serial number second case
(iii)                if field pstyp eq 3 then it is PO using serial number with    subcontracting third case.
Please guide how to do this scenario.
IR:
1)       how many data types I need to create
2)       how many message types I need to create
3)       how many message interfaces I need to create
4)       how many message mappings I need to create
5)       how many message interfaces I need to create
ID:
1)       how many receiver determinations I need to create
2)       how many interface determinations I need create
3)       how many receiver agreements I need to create
And where to write the conditions at message mapping level or at receiver determination level.
Kindly provide solution to every point.
Regards,
Venkat.

1) if no condition is specified then it is standard PO first case
2) if field tdline ne space then it is PO with serial number second case
3) if field pstyp eq 3 then it is PO using serial number with subcontracting third case.
you have to create
1. outbound ( IDOC)
2. 3 Inbound (same MT)
create 3 mapping program each for 1 condition
create 3 interface mappings
ID:
1 reveri BS.
3 Interface determinations, so 3 receiver agrement.......
you can put the condition on the mapping or in the condition tab of the interface determinations.

Need to e-mail job log after job completes (SM37)

Greetings!
I need to export the results of the Job Log (run SM37, double-click a finished job and then click "Job Log" button at top - this is the list I need). Obviously, the program has already terminated so it won't be able to initiate it. Is there another way?
The need is to have this log be e-mailed automatically after it's ran or, at the very least, have a second "step" (job?) that reads the previous one and e-mails it's log.
We'd like to keep it automated and not have someone in operations have to remember to do this.

Hi,
Debugging can be done as follows:
1. Put a breakpoint at the beginning report CRM_MKTTGGRP_EXPORT_BATCH
2. Select your previously executed job in transaction SM37
3. Type 'jdbg' into the tcode field in the upper left area
To analyze the results and messages of the campaign execution, you can also have a look into the application log, either in the campaign application or in transation SLG1. There you should find details why the BPs have not been contacted.
Hope this helps,
Frank

"iTunes was unable to verify your device" after succesfully completing recovery mode on iPhone 4

I have an iPhone 4 which has never caused me any problems, until i updated to iOS7 it started lagging and battery didn't even last until midday (having it charged 100% in the morning!).
In just a few days it turned off automatically and wouldn't turn on. I googled and solved it by pushing the two buttons together for about 10 seconds. iPhone revived, and all the data was intact though many people states it would've been erased.
The morning after, using my iPhone more carefully not to have it crash again, it crashed. 10 seconds wouldn't do and I gave up, until the day after I found by surprise that the battery had run out and it finally showed some sign of not being completely dead!
I connected the cable to iTunes and pushed the Home button before connecting the iPhone and it entered Recovery mode. Recovery mode was completed and the iPhone had to restart to complete the process. While completing I get the error message "iTunes was unable to verify your device, please disconnect and reconnect your device". And from here I don't get anywhere, so I will probably visit Apple Store and ask what can be done, but if anyone has had the same problem please share any possible solution to this problem!

I had to contact Apple Store and make an appointment. They tried the last step suggested (which I had already tried three times) and stated that the memory had failed. They said it probably failed due to having some small issue already on the phone and then updating to a new iOS.
They could only offer me an exact copy of my iPhone but new for 149€.

R/3 to XI (Idoc to File): Do we need to maintain distribution model in R/3?

Hi All,
I have a very basic question regarding Distribution model.
My scenario is IDOC-->File ( SAP R/3 --> XI). So all I am trying to do is send the IDOC frrom R/3 to XI. ( Within XI I am going to do an FTP to the 3rd party file server)
I have created a distribution model, but was wondering if I really need to create one as message is going from R/3 to XI and not from R/3 to another R/3.
Please help let me know If I need to distribute this model to XI or to SAP production sytem or I do not need to duistribute at all for this scenario.
Thanks
Shirin

Hi,
if you create partner profiles and port via t.code.
i hope, it's not required to maintain Distribution model.
please check the below points.
Configuration Steps for Idoc to File Scenario.
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO, SETTINGS IN SAP-XI
STEP 1:ALE SETTINGS IN SAP-XI
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) ALE SETTINGS TO POST IDOC OUT OF SAP-R/3 ***********************************************************************
a) Create RFC Destination using T.code in SM59.
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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item u2018Generate Partner Profilesu2019
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> u2018Distributeu2019 to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
warm regards
mahesh.

IDoc-to-File: Status=processed succesfully but file is not always delivered

Hi Experts,
I have a problem with a IDoc-to-File scenario. I generate an IDoc and send it to the XI-System. Afterwards a XML-file is created which should be transmitted to a filesystem or to a ftp server (I tested with both). In the SXMB_MONI the Message has the Status "Processed Succesfully" and the Acknowledgement-Status "Still awaiting acknowledgement". The problem is that not all files arrive the destination succesfully. sometimes they arrive and sometimes not. and always the same status in the sxmb_moni.
if a message not arrived the destination, in the message monitoring in the runtime workbench there is the status "To Be Delivered". If one Message has the status "To Be Delivered" the following messages get this status too.
the communication-channel-monitoring says that "the communication channel is correctly configured and started"
Can you help me? I don't know where the problem is. could it be that the adapter-engine has some problems?
Thanks and best regards
Christopher

hi,
I clicked on details in the message monitoring but the fields "error category" and "error code" are empty. Then I checked the audit log in the message monitoring. there are the following three entries
2008-01-28 14:08:56 Success Message successfully received by messaging system.
2008-01-28 14:08:56 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-01-28 14:08:57 Success Message successfully put into the queue.
and here the audit log of a message which could be transmitted correctly:
2008-01-28 10:33:10 Success Message successfully received by messaging system.
2008-01-28 10:33:10 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-01-28 10:33:10 Success Message successfully put into the queue.
2008-01-28 10:33:10 Success The message was successfully retrieved from the receive queue.
2008-01-28 10:33:10 Success The message status set to DLNG.
2008-01-28 10:33:10 Success Delivering to channel: FILEPORT_TO_PICC
2008-01-28 10:33:10 Success MP: entering
2008-01-28 10:33:10 Success MP: processing local module localejbs/CallSapAdapter
2008-01-28 10:33:10 Success File adapter receiver: processing started; QoS required: ExactlyOnce
2008-01-28 10:33:10 Success File adapter receiver channel FILEPORT_TO_PICC: start processing: party " ", service "X22_PICC"
2008-01-28 10:33:10 Success Write to file "/tmp/xi/PICC/INV_5075_4000102108_20070109_103310.XML" as binary, size 410 bytes
2008-01-28 10:33:10 Success File processing complete
2008-01-28 10:33:10 Success MP: leaving
2008-01-28 10:33:10 Success The message was successfully delivered to the application using connection File_http://sap.com/xi/XI/System.
2008-01-28 10:33:10 Success The message status set to DLVD.
2008-01-28 10:33:10 Success Acknowledgement creation triggered for type: AckNotSupported
2008-01-28 10:33:10 Success Acknowledgement sent successfully for type: AckNotSupported
can you say me where the problem is?
thanks and regards
chris

Examples needed for Idoc to file and IDOC to web services

Hi ,
Could any one of you give some examples which take me through step-by-step in building IDOC-TO-FILE and IDOC-TO-WEB SERVICES?
Regards,
XI Developer.

Hi,
For IDOC scenario you need to first do the required configuration:
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Testing purpose u can use the below method:
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters --> For Idoc sender: IDOC -file
IDOC configuration:
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
SOAP scenario:
YOu have to first create the WSDL through ID and import that WSDL in to IR external definition.
Refer the below thread and pdf:
How to use SOAP adapter:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
SAP AII - How to consume and expose webservices ?
Thnx
Chirag
reward points if it helps.

IDOC to file....bpm or without bpm...help needed..

Hi XI friends,
its IDOC to file Scenario..
its daily scheduling report..if we run that report.....Number IDOCs are generated in SAP..
we have 5 legacy systems..
for one legacy systems file type is .txt file and for remaining xml files..
the catagarization based on one of the field in IDOC..
if that field is 01 the file type should be .txt file
for others xml file..
if that field is 01 then ..XI need to collect all the IDOCS into one .txt file for other values direct conversion into XML file i.e..each idoc gets into one xml file
if that filed is 01..then XI need to collect all the IDOCs in that day into single .txt file and the fileds are Fixed lenghts...and at the same time ..that idoc contains number of segments ..if any Idocs doesnt contain some segments..ther should be no more blank lines...each segment should placed in new row...and also..for some segements ..XI should collect into seperate .txt file....
please help me....how to achive,,,,,,
regards
Munna

if that field is 01 then ..XI need to collect all the IDOCS into one .txt file for other values direct conversion into XML file i.e..each idoc gets into one xml file
if that filed is 01..then XI need to collect all the IDOCs in that day into single .txt file and the fileds are Fixed lenghts...and at the same time ..that idoc contains number of segments ..if any Idocs doesnt contain some segments..ther should be no more blank lines...each segment should placed in new row...and also..for some segements ..XI should collect into seperate .txt file....
in this case BPM will be required to collect the IDOCs ref: http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
base the correlation on the field that contains the value 01
also then later using XPATH in your receiver det. you can check for the value and route the message to the particular receiver as u want to
ref:
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers

Need information regarding IDOC to JDBC Scenarios.

Hi,
Kindly help me with the pre-requisites inorder to start with a scenario of IDOC to JDBC and also the scenario of JDBC to IDOC.
Regards,
Sreedhar, Av

Hello Sreedhar,
While we working in JDBC or JMS Adapters we should deploy the Drivers..
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
To install JDBC driver follow the how to guide.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
Configuration of JDBC Adapter for SQL Server
JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
UserID and Password.
If the connection is not working find the correct port number.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
JDBC- X I - R/3 Scenario
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
2) While we working in IDOC Adapters we should do ALE Config of IDOC Settings .
Do these configurations in R/3 and in XI...
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.
Here in IDOC to JDBC interface we need not to config sender Adapter..
1) The main usage of a sender adapter is to convert the input format into the XI supported XML format.
Once the conversion is completed the sender agreement appends the header with the sender details.
In case of these adapters we wont require sender agreement and sender communicationchannel for the
following reasons.
Sender agreement is associated with a namespace when we shoot an idoc frm r/3 if already contains its standard sap namespace. so those is need of sender agreement
The sender communication channel use is to identify the sending system and adapter, as the idoc header contains the details there is no need to sender.
These adapters resides on ABAP stack here the integration server takes care of IDOC/HTTP to XML conversion without requirement of adapter.
The business system that is sending the adapter has already been assigned to a techinical system which normally acts as an integration server...
IDOC to xi links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Hope this explanation is useful to u..
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on Jun 3, 2008 9:57 AM

Need an alert to be sent after succesful completion idoc to file scenario.

Similar Messages

Maybe you are looking for