File to Idoc Scenario using third party systems

hi,
Working with a File to Idoc Scenario. Been able to successfully define everything in IR / ID. However when I go to BD87 (reciever system) and see the status of Idoc processed - getting the error code 51 "Function Module Not Allowed: <Function Name>" . What could be the reason for this???
Have defined partner profiles in WE20 of type LS and also specified an inbound paramter in the post processing tab for partner profile. Are there any other settings I need to take care of to avoid getting that error.

Hi
I am giving u all the steps whioch are required for
<b>File to IDoc</b> Scenario
SM59- Create RFC destination
IDX1- Create a IDXPORT in idx1
IDX2-3. Import metadata of IDocs in idx2
Bus. service adapter specific Identifiers-->Logical sys name
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
SE16-Table name->LFA1 to check vendor has been created
Check have u followed all the steps.
Regards
Arpit Seth

Similar Messages

File to IDOC Scenario using BPM

Hi Experts,
    I am working on file-Bapi-Idoc scenario using BPM.
    I have two conditions
1. If the Sonumber is populated then need trigger an Bapi_change
2.If the Sonumber is not populated from the file then need to trigger a Bapi_Createfromdat to create the sales order and receive the salesorder number as response from Bapi
and the response of these BAPIs should be validated whether the Bapi is successful or not.
If it is successful message then need to trigger IDOC or else should throw an alert message.
let me know the steps involved in this scenario.
can i send alert message to other email IDs or can i send it to only XI admin?
Please let me know u r inputs.
Thanks in advance
Praveen

Hey,
You need to have a BPM for this.
BPM design.
Recieve step(abstract asynchronous) for file structure
Switch Case(condition whether sonumber is populated or not)
if populated
Branch 1(of switch)
    transforamtion step:- mapping between File and Bapi_Change(Request structure)
Send step(abstract syncronous) To send the BAPI_change
Branch 2(of switch)
transformation step:-mapping between file and BApi_Create
Send step(abstract synchronous) To send the BAPI_Create
Block step(which will include the Switch step)
    trigger an Execption in case of an error(in any of the two branches) through the block
    The Exception will trigger an alert.
Now after the Block step there will be a transformation step(which will have the mapping between RFC response and Idoc)
Next is the send step(abstract asynchronous) for the idoc
In case if there is no exception the Idoc will be triggered or the exception branch will trigger the alert
rewards points if useful
regards,
      Milan

File to IDOC scenario using FTP server

Dear Experts,
I'm getting IDOCs in the form of .TXT file from sender side and at reciever end we have IDOC. We are using FTP connection at sender.
I want to know:
1. Is FCC the only solution to integrate with PI or do we have any other option also?
2. What all the things I need to care in designing and configuration?
Thanks a lot.

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.

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

Howto Send IDOC to third-party system. programID can not be registered.

Hi, guys.
I want to post IDOC to a third-party system through XI. And for sure, the third-party system can receive IDOC.
In the receiver communication channel, I would fill in the RFC Destination with a RFC connection defined in SM59.
In SM59, it is a tcp/ip connection and in technical settings the activation type is Registered Server Program. I name the Program ID randomly with 'a.a'. In Gateway Options, I fill the host with XI server and service with sapgw01.
Then I test the connection, the result is program a.a not registered on XI server.
My question is how to register the progam when I want to use this RFC to send IDOC to the third-party system. And how the RFC know which system he would connect. I don't find anyplace with the connection information such as IP or something like this.

Sergio Cipolla
Thank you for your material. I have read the doc you refered.
Almost I understand the process, there is one part.
I should register the program ID in saprfc.ini file with the following content:
DEST=FROMXI
TYPE=R
GWHOST=saphost
GWSERV=sapgateway
PROGID=a.a
Here I am wondering the fiield "DEST" represent for. Does it mean the hostname of the target external system?
And Here is the UNIX system, what is the path location of the file saprfc.ini or where I should put this file to be effective.
Thanks in advance.
Bu Ju

File -- IDOC scenario using XI 3.0

Hi
I tried out a simple flat file to IDOC scenario using XI as the middleware and tried to post documents of type CREMAS03 on the backend R/3 system.
Now, I see that there is an IDOC number generated in the XI layer by the IDOC adapter. This IDOC number is seen under <SAP:DOCNUM>XXXXXXXXXX</SAP:DOCNUM>in the
Response-->IDOCOUTBOUND section of the pipeline in SXMB_MONI
According to SAP documentation :
<b>To enable you to select IDocs in the target system later on, the system transfers the message GUID and the IDoc number in the ARCKEY field of the IDoc control record.</b>
Now, I do find the XI msgid given as arckey in the control record of the Inbound in the target R/3 backend system. But I cannot find the XI IDOC number being cross referenced in the control record of the IDOC in the R/3 backend.
1.Is there a way to cross reference the IDOC number in XI with the IDOC number in the R/3 backend ( we have two different IDOC numbers, right ) i.e a IDOC number to IDOC number cross referencing in this File-->IDOC inbound into the R/3 system scenario involving XI
2. In the XI box, do we get as a part of async.reponse from the R3 system, the IDOC number that is created within the R3 system ? This would serve directly as a cross reference. Or do we have to indirectly query EDIDC table in the R/3 backend with the arckey value = msgid in XI - to retrieve the IDOC number created in the R3 backend ?
Thank you in advance for your time.

Hi,
Pls look into following link about Acknowledgement.
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
Pls note that , you can't get/receive the Acknowledgement for Sender File Adapter. Because File System acts as an Async system. But you can get the Idoc response and you can write it into another file. For this you need to use BPM.
Hope this helps..
Regards,
Moorthy

Third Party System In SLD??

Hi Friends...
i need to use third party systems in my scenarios..
for third party Business systems and Technical systems ..is this mandatory to provide Logical systems and host names in SLD.
regards
Ram

Hi,
I hope no..But..
Unlike SAP products, third-party products are not necessarily included in the SLD component description. Therefore, you must first register the third-party product before you can register an installed system of this third-party product in the SLD.
See below link..
http://help.sap.com/saphelp_nw04/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
Regards
Chilla..

Decryption of Account Number Send By Third Party System

Hello,
We are processing CSV file sent by one of Third Party System.
Earlier we used to receive plain text account number in this CSV file. For this month, Third Party System has sent this Account Number in Encrypted Format.
My Question is how can I decrypt this Account Number so as to get it converted in Plain Text ?
If I get Private Key / Shared Key used by Third Party system for encryption, How can I use it in People code so as to decrypt the account number ?
Thanks in Advance.
Atul.

Hi Ram,
of course you cannot supply the WSDL URL. Inside the WSDL (just view it in your browser) you find (usually but not necessary) towards the end something like
<soap:address location="http://www.weather.gov/forecasts/xml/SOAP_server/ndfdXMLserver.php"/>
which is the actual adress of the service.
An example service can be found here:
<a href="http://www.weather.gov/xml/">National Digital Forecast Database</a>
containing the WSDL URL at
<a href="http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl">this address</a>.
You might also want to browse for the amazon webservices which allow you to embed queries against amazon into your application.
have fun,
anton

Where to define third party logical system name in file to idoc scenario

Hi Friends,
I am shalini shah.
I have one doubt, where I can define the logical system name in File to Idoc scenario.
I created Logical system for R/3 system in SALE t.code, but where to define the Third party logical system ,
In SALE or any where.
Please give me solution.
Warm Regards,
Shalini Shah

Hi Shalini,
You need to create Business system in SLD and import the business system in ID.Then u will start with the configuration.
Just refer the below link for configurations with step by step solution.
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)&
Thnx
Chirag

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

IDoc Scenario SAP ERP - PI(Receiver IDoc Adapter) - IDoc to Third-Party system

Dear All,
I have created a scenario to send IDocs via PI system (PI 7.1) to a third party system.
There is no message mapping involved(Only ID part)
I have imported Idoc Metadata from the source ERP system.
Created an RFC destination(BC_ERP_SEA) in the PI system of type TCP/IP with registered Server Program to third party system.(Tested success)
Created a port in IDX1 BC_ERP_SEA with above TCP/IP destination.
Receiver communication channel of type IDoc is created with the following parameters:
         RFC Destination: BC_ERP_SEA
         Segment Version: 640
         Interface Version: SAP release 4.0 or Higher
         Port: BC_ERP_SEA
         SAP Release: 640
Now when I execute the scenario, I get the following error in SM58 of PI system.
Bena IDOC_INBOUND_ASYNCHRONOUS not found on host.
Request your help for this issue.
Thanks,
Jishi

Hi,
Check below steps..it may resolve your issue
1. It is mandatory to specify Ack Destination value in IDoc_AAE sender channel. The value should be an RFC destination name which is connecting to your SAP ECC system.
2. In inboundRA resource adapter, the value for the property "local" should be set to "true".
Regards,
Tulasiram.

File Adapter and Third party system

Hi,
I am new to XI and implementing a simple scenario.
In SLD- I have 3rd paty software component and product.
3rd party technical system: using my pc - For host name I am using my machine name.
Scenario: Using file adapter transform csv file to xml.
File resides on my machine. I have configured file adapter inbound and outbound. Integration Dir & Rep objects are all activated.
But nothing happens, cannot see any message in Messgae monitoring..
Any help would be great.. Is my technical system setup wrong?
thanks

chk whether the folder in your m/c where the CSV file resides is shared and has appropriate access. Also you need to specify your m/c IP with fwd slashes, e.g) //<Ipaddress>/foldername
configuring your m/c as a Third Party system in SLD is fine.
If you think ur SLD settings are not correct, you can define your file adapter commn. channel in a Business Service(which does not require an SLD entry) and check whether it works.
Thanks
Saravana

ECC Via XI to Third Party system through Idocs

Hello,
I have done all the setting required to IDOC communication,
RFC's are created,
Distribution Model
Imported the Meta data
Partner Profile
ESR Objects Made (IDoc as my Source and WSDL as External Definition for Target)
ID Configuration made, sender channel is SOAP.
SLD Configuration (Business and technical system as third party systems and ECC as ABAP system)
Sender is ECC, no sender channel will be required (correct me if i am wrong), where as
now when i test my scenario with WE19, i do not see my XML while using tcode sxi_monitor.
have i missed any step.
Any help will be appreciated,
Regards,
Abhishek

in IDX5 System is not a Central Integration System: unable to start program is the error, if i fix this error what will be impacts on the system
please follw bwlow step:
Check SXMB_ADM --> Check the Integration Engine Configuration
In the Global Configuration Data :
Role of Business System should be Integration server
Corresponding IS should point to Pipeline URL.
please check below link
Configure Role of Business System " as Central Integration Server , PI
and
Transaction SAP Adapter u2013 Monitoring (IDX5) : provides you with an overview of all messages sent to or from the Integration Server as IDocs. Double-clicking a message provides you with detailed information on this message in the Integration Server.
You can monitor the status of all XML messages by using transaction Integration Engine u2013 Monitoring (SXMB_MONI).
You can use transaction SM58 to monitor native RFC communication on the Integration Server. This type of communication protocol is used in two places here:
To send an IDoc from an SAP system to the Integration Server
To send an IDoc from the Integration Server to an SAP system
and one more thing are you tested Rfc destination ? is it working ?

System Level Acknowledgement in File to IDOC Scenario

Hi All,
I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI should send a acknowlement file back to the sender system.
Could someone suggest how to design this scenario?
Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

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.

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
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.
Thanks,
Satya

File to Idoc Scenario using third party systems

Similar Messages

Maybe you are looking for