Salary IDOC to File system

From R/3 we are sending our Salary Info IDOC to our EXTERNal Payroll dept.
In R/3 We are running a job and that will produce 250 IDOCS and this has to be collected in the Receiver File System.
Should I need to use a BPM for the above scenario? Or once my job runs in R/3 using my 0..N Message structure, I can do the necessary mapping and send it to the Receiver file system.
Thanks.

Jenni,
You need BPM or as Ahmad suggested in the previous thread u can use file system.
Ahmad,0..n occurrences is applicable only when XI send IDOC's to R/3, not in the other way around. If R/3 wants to send IDOC to XI the other option of collecting IDOC is IDOC Packaging concept.
If I'm not wrong, the IDOC Packaging will pack the IDOC's in R/3 and finally sents to XI if criteria is reached, let say 500 KB , etc... Even in this case u need BPM to collect the messages.
Best regards,
raj.

Similar Messages

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

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.

IDoc Adapter - Logical System - File to IDOC configuration

I have a scenario reading a File ->XI->IDoc in R/3. I'm looking to have the control record parameter for SNDPRN reflect the Environment dealt with. I unchecked the 'Apply Control Record Values from Payload' & 'Take Sender from Payload' boxes but the problem I'm getting is that the system is reading from the business service (IDoc Adapter - Logical System) and feed it in the Partner Profile in the IDOC. This means that I should all the time redefine 3 this Logical System in config before transporting my scenario from DEV/QA/PRD. Any idea how I can avoid this kind of 'hardcode' ?
Thanks

Hi,
Why u r using three different LS can't u use only one LS and send all the IDOCs to same LS. That will ease ur task.
Do let me know why u r going for three different LS.
In the file r u getting any data which will help u to identify that this file is for which LS. IF that is the scenario then u can use the value mapping and based on the value which is coming in file u can map it to the IDOc filed which u have mentioned and in the configuration it will take the respective configuration.
Thnx
Chirag

XI and R/3 System connection settings for IDOC to File scenerio.

Hi SAP champs,
I am working on a IDOC to File XI scenerio. But I am confused while configuring connection settings at XI system and R/3 system. I am finding problem in transaction IDX2 to maintain the IDOC metadata. Please let me know the complete step by step system cofigurations in XI and R/3 systems for the scenerio. Thanks in advance..
Regards
Sanjeev.

Hi Sanjeev,
We upload Medata in IDX2 to just reduce runtime effort and hence to improve the performance. However it is not a mandetory step to be performed for R/3 TO XI scenario.
You are confused just because here you dont find any F4 help to select the metadata and the PORT.
Thanks
Sunil Singh

Problem IDOC to File scenario: No service for system SAPIDC, clnt in ID

in IDOC to File scenario, when IDOCis triggered from R/3 to XI, it gives error in SM58 transaction
"No service for system SAPIDC, client 800 in Integration Directory"

In a scenario, i have a BPM which has a transformation step which contains a mutimapping ...means 2 messages mapped to 1 messgaes, here in the mapping i m using an UDF and written code to extract the file name from dynamic configuration.....
the problem is ...the same BPM contains another transformation step which contains a message mapping (which is not multi mapping), and here the code (UDF) works to fetch the file name...
the code is all correct....and it looks like
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String sourceFileName = conf.get(key);
if (sourceFileName == null ){
sourceFileName = "ErrorFile.xml";}
return sourceFileName;

IDoc-to-File with ext. Partner ... How to define the third-party system

Hi all,
I want to make an IDoc-to-File scenario with an external partner. the xml-file generated by the integration server should be forwarded with the file/ftp-Adapter to a ftp-server in New York (our XI-System is in Germany).
Is it right that I have to create a technical system and a business system for the ftp-server in New York? I want to create it as a third-party system. But how? Is it enough to give only a name for the third-party technical system?
What I have to put in "Host name" or can I leave this gap empty? And have I to choose Products or is it not nessesary?
Thanks for your answers
best regards
Christopher Kühn

>
> Is it right that I have to create a technical system
> and a business system for the ftp-server in New York?
Yes it is the correct way to do this.
> Is it enough to give only a name for the third-party
> technical system?
> What I have to put in "Host name" or can I leave this
> gap empty?
Dont remember exactly. But I think HostName is mandatory. You can give any value that you want here. Does not matter at all.
Ideal way is to give the HostName of the FTP server here. if unknown give any value.
And have I to choose Products or is it not
> nessesary?
>
Not necessary. But ideal would be to assign the products which you have created in the SLD for your XI content so that the SWCV is also associated with this Tech System
Regards
Bhavesh

Receiver Business System Connot find Inbound Interface - IDoc to File

Hi Everyone,
I am doing IDoc to File Scenario.....Idoc got triggered from SAP system and successfully posted to SAP PI.
Now when I check in T-Code IDX5 in PI, I got one message. When I double click that I am getting following error:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also When I am selecting Receiving Inbound interface for Receiver system, I am not getting any interface by default.
Please help me out.
Thanks & Regards,
Sudheer

Hi everyone,
Thanks for your quick responses.
Actually I am doing IDoc to File Scenario from blog which consists of Conditional Receiver Determination
"SNDPFC"
Here is the Explanation given in that blog:
In most instances, a new Receiver Determination would be created. However, given that in this scenario the combination of the sender service (i.e. u201CGL1u201D) and interface (i.e. u201CMATMAS.MATMAS04u201D) will be used by every student, each student will instead be adding their receiver service to an existing Receiver Determination
11. In the Condition column on that same line, left click on the question mark help icon
12. In the following Condition Editor pop-up window, left click on the help icon in the u201CLeft Operandu201D field
13. In the following Expression Editor pop-up window, select the u201CContext Objectu201D radio button
14. Use the drop drown to locate and select the u201CSNDPFCu201D field and u201COKu201D
15. Back in the Expression Editor, leave the u201C=u201D Operand as is
16. Enter your group number in the u201CRight Operandu201D and u201COKu201D
17. u201CSaveu201D and validate your u201CConfigured Receiversu201D as seen below:
I did not understood this Conditional RD.
Apart from this all configuration are correct.
Thanks,
Sudheer

From ONE file to Many IDocs in many systems

Hi,
In my scenario i have the input file like below
HEADER;EMPNO;EMPNAME;TARGETSYSTEM
ITEMHEADER;DESG;LEVEL
HEADER;EMPNO;EMPNAME;TARGETSYSTEM
ITEMHEADER;DESG;LEVEL
HEADER;EMPNO;EMPNAME;TARGETSYSTEM
ITEMHEADER;DESG;LEVEL
Here TARGETSYSTEM values are SAPG1,SAPG2 and SAPG3
for each one HEADER and ITEMHEADER i have to create one idoc in the respective receiver system based on the TARGETSYSTEM value.
Based on the TARGETSYSTEM value, idocs should be created in to the respective system.
But problem is :
Its creating 3 idocs in first system, same 3 idocs in second system and same 3 idocs in third system also.
But i want to create one idoc in 1st system and second idoc in 2nd system and third idoc in 3rd system based on the TARGETSYSTEM value.
please help me, how to solve this problem
Thanks & Regards,
Vijji

Hi Vijaya laksmi,
I have seen ur question.
appriciate for doing file to muliple idocs first
without BPM, u can do this scenario ok
but while doing this scenario, u have to do idoc with max occurence ie first, after importing idoc, u have to export to xml file and change occurence inplace of "min occurence " write " min. occurence and Max. occurnce=" and then import this in External definition then u can use this in scenario for multiple idoc. Here don't require more interface mappings ok. u can do this only with one interface mapping. while generating idoc, at the time u have to save and send as multiple idocs how many u have to send to receiver systems just give the no how many idocs.
Even though you won't get it i will send file to multiple idoc scenario ok
all the best
regards
Peera

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 .

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

What all configurations to do in SAP R/3 to send an iDOC to XI system

I want to send an idoc from an SAP R/3 ECC5.0 to an XI system Netweaver 04's.
Pls let me know the STEPS I HAVE TO DO IN MY r/3 SYSTEM .
I have created the RFC destination in R/3 and XI system but still the idoc is not going into XI system.
It would be a great help if i can get step bu step guide for the configurations i have to do in R/3 .

Hi,
First check the status , with we02
Also see the below links
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI. Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
Regards
Chilla

Picking a IDOC Flat File stored in SAP R/3 Application Server by SAP PI

Hi,
Can SAP PI pickup a IDOC Flat File stored in SAP R/3 Application Server Directory and send it back as an Inbound IDOC.
Scenario:
We have a data in the EXCEL Sheet, which will be used to a fill an IDOC and the IDOC will be just save in the SAP R/3 Application Server Directory, but can not be triggered due to its peculiar behavior. Afterwards, SAP PI should pole the SAP R/3 and pick up that IDOC Flat File from the R/3 Application Server and send it back to the SAP R/3 as an Inbound IDOC.
For Ref: IDOC does not have a Outbound Process Code, thus can not be triggered and send to SAP PI. It is always used as a Inbound IDOC in SAP R/3 system.
Regards,
Saurabh

SAP PI should pole the SAP R/3 and pick up that IDOC Flat File from the R/3 Application Server
If SAP PI = 7.11 --> /people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
send it back to the SAP R/3 as an Inbound IDOC
why to send some information again into R3 which it already has? cant some internal code in R3 read the info from excel and then update the IDOC directly?

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.

Hi, guys: hard to understand XI IDoc to file,

I have work through this scenario. My colleague have problem to understand it. I think it is a little hard to explain it.
About logical system, We can say ERP send IDoc to XI , and XI convert it to file. and then the logical system name should be XI client's. But in XI, we always define business system or business service for other systems not XI itself. And service FTP2 must have a logical system for IDoc related scenarios , others(RFC,JDBC, file and etc) don't need.
When we define logical system and partner profile for file system, we use RFC destination from ERP to XI.
For ERP A to ERP B, it is easy to understand, we should define logical system for B system in A , which is identical in B.
logical system, partner profile in SAP ERP, and business service/ business system in XI are both to represent a (logical)business system.
-- if ftp2 use logical system of XI, then another system can't use it. and maybe it can't work, business system can't use XI's logical system.
Any ideas? Am I right?

HI Shen,
You are try to understand this bit complicated concept is on right track.
Let me explain this step wise.
1. About logical system, We can say ERP send IDoc to XI , and XI convert it to file. and then the logical system name should be XI client's. But in XI, we always define business system or business service for other systems not XI itself. And service FTP2 must have a logical system for IDoc related scenarios , others(RFC,JDBC, file and etc) don't need.
---->
Here XI is just middelware so While sending the IDOC from R/3 to XI you need the Logical system with Receiver Port as directing to XI client. The Receiver Logical system is not imp. incase of sender IDOC.
But when you will be sending the IDOC from XI to R/3 then the Logical system should be maintained, because the inbound IDOC processing program will work as per the details of Contorl IDOC and the Logical system that will point from XI. This will not be the case for other RFC, JDBC, file etc, as they don't have any kind of Control -Records to be maintained.
2. if ftp2 use logical system of XI, then another system can't use it. and maybe it can't work, business system can't use XI's logical system
---->
Yes, Once you have used the Logical system name in any of the Business service or Business system then you can't re-use it. This makes possible the feature of Re-usability. You can create the multiple communication channels under this Business service/system
Hope this will be clear now
Thanks
swarup
Edited by: Swarup Sawant on Jun 25, 2008 10:24 AM

Salary IDOC to File system

Similar Messages

Maybe you are looking for