Issues in SAP(Idoc)-XI-File scenario
Dear All,
I am working on SAP(Idoc)-XI-File scenario. But in the Receiver agreement i am not able to see the idoc in order to specify some conditions there.
Please suggest if I have to do any settings in order to specify some conditions in the idoc.
Warm Regards,
N.Jain
Hi nishu jain ,
U can specify the conditions in Reciever Determination.
1.Go to Scenarios
2.Choose your business scenario
3.Click Service without party
4.Double click Reciever Determination
5.U wil get screen in which there is a option called Configured Recievers.
6.Click there.then u wil get the screen with
Left Operand Op Right Operand
7.There u can specify the condition.
Reward points if u find this useful.......
Regards,
gyanaraj
Similar Messages
-
Getting Receiver Agreement issue in IDOC to File scenario
Hi Gurus,
Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
Error Message:
No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
Error Category : Outbounding
Error ID : CO_TXT_OUTBINDING_NOT_FOUND
My IR design:
Sender:
Interface : VEND_IDOC_OUT_MI
Message Type : CREMDM.CREMDM04
Receiver:
Interface : VEND_FILE_IN_MI
Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
My ID Config:
1. Sender / Outbound Message: Service Type --> Business System
Service ---> SAPERP
Interface--> VEND_IDOC_OUT_MI
Adapter Type : IDOC
2. Receiver / Inbound Message: Service Type --> Business Service
Service --> IDOC2FileReceiver
Interface ---> VEND_FILE_IN_MI
Adapter Type--> File
3. In Sender Agreement : Specified the Sender Communication Channel
VEND_IDOC_OUT_Channel
4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
Can anyone help me identifying what's going wrong. I'm very new to XI and basically this is the first assignment I'm working on.
Regards,
SubhadipHi Babu,
In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
Please find the XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
<xsd:complexType name="VEND_FILE_DT">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8f584d80456311dccd680018fe79f69b
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a8653cb0390c11dc843000188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor Code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a8653cb4390c11dc84e800188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor name4
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a8653cb5390c11dcbe3400188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor City
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a8653cb6390c11dc896100188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor PO Box
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4811db0335fd11dc9e9600188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor House No & Street
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4811db0435fd11dc98b000188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor Postal Code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4811db0535fd11dc870500188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor Country
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
7ca8d600403b11dcc9bd00188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Tax Number 1
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9abaee7040e611dcce4300188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Telephone number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9abaee7140e611dc8f3900188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
VAT Registration Number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9abaee7240e611dccef700188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Account Number of Vendor or Creditor
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9abaee7340e611dcb3bc00188bd09370
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema> -
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.
RajuTo 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 -
Error in IDoc to file scenario
Hi Experts,
I am working on IDoc to File scenario.IDoc is sccessfully reached XI.In SXMB_MONI it is showing error in request mapping.Error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please suggest me in this issue.
Thanks,
Bhuvan.Check this link:
http://help.sap.com/saphelp_nw70/helpdata/EN/bb/ad1c3d2b058c4ce10000000a114084/
You might want to refer to the SAP NOTE: 316877
Regards,
Ravi -
Problem in idoc to file scenario
hi
while creating the idoc to file scenario i am facing few problems.
1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
3) i am using my ecc6 training server as my sender and using my XI server as receiver.
4) i am sending idoc from ecc6 and converting it to file in XI server and saving it in XI server itself(my receiver in this case).
my error:
i send my idoc from we19 transaction, and i see a error message stating
that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
my doubts.
1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
kindly help me with this issue.
regards
manoharan>
manoj murugesan wrote:
> 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
>
> 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
>
> 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
>
>
> kindly help me with this issue.
>
>
> regards
> manoharan
and to 1 & 2 ref. below,
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
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
3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP -
Hell Experts,
I have done desgin and configuration from Idoc to File Scenario in XI Intergration server.
Source is R/3 and Target system is File. I have successfully configured each and every step. Send Idoc from R/3 to Intergration server and run sxi_cache. But I didn't get successful results, always the error message shows in SXMB_MONI as follows:
Ackn Status contains system error
During the application mapping com/sap/xi/tf/_CUST_MMAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeExcep
tion in Message-Mapping transformatio~
Exception of class CX_XMS_SYSERR_MAPPING
My system Patche level as follows:
SAP_BASIS 640 0012 SAPKB64012
SAP_ABA 640 0012 SAPKA64012
PI_BASIS 2004_1_640 0009 SAPKIPYI69
SAP_BW 350 0009 SAPKW35009
The above error is related to patches problems or any Mapping problems ?
Please help me.
Advanced Thanks.
Regards,
ChandraHi,
This may be a mapping issue, try this:
a)in interface mapping see if grids are formed at source and target after executing the test option,
b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
i am not sure of the patch levels.
Regards,
Anirban. -
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,
SreeHi 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 -
Setup for IDoc-XI-File scenario
Hi All,
Please provide info where can I find, step by step documentation for the basic setup on R/3 and XI areas, before start developing IDoc-XI-File or File-XI-IDoc scenarios.
Thank you,
SreeHi,
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:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
File -> IDOC ->
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
(It concentrates on XSLT mapping but also gives an idea about the configuration part. Do go thru that, it might help you.)
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
I hope I have answered your query.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS. -
XI: idoc 2 file scenario( Contain error in SM58)
Hi experts,
Here i am having one issue. i have done Idoc 2 file scenario...i have created material in R/3 successfully. when i have sent the material to legacy system..Idoc was generated Successfully in r/3 but i haven't seen that message in SXMB_MONI..
i got the error message in SM58 i.e. IDX1 port SAPDE1, Client 220, RFc Destination Contain error.
plz any one can u help me on this....
Regards,
YadavHi Yadav,
The RFC port you defined is not correct in IDX1. The Port name must be in the form of u201CSAPxxxu201D, where xxx is the system ID of the backend SAP system.
Just cross check it.
Check this for more details:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Regards,
Sachin -
Regarding remote login in IDOC to FILE Scenario
Hi Friends,
I have been struggling from this issue from many days.
when i am doing IDOC to FILE Scenario, i was posting an CREMAS03 IDOC from ECC client 800 to SAP XI Client 001.
After executing WE19 in SAP ECC, its automatically asking for XI login detals.
will it really ask for login details.
<b>Because if we do FILE to IDOC Scenario, it wont ask for login details.</b>
If i check RFC destination from XI to ECC, we could easily remote logon to ECC without asking for any logon details, but if i check RFC destination from ECC to XI, <b>its asking for Lodin ID and Password</b>.
Regards,
Varun Reddy.KHI Varun
Check the roles assigned to you.
The roles are...SAP_XI_ADMINISTRATOR and SAP_XI_DEVELOPER.
If u have created the user in SU01 just now..and checking logon to IB immediately ..it will not come cos it takes some time for the users to get reflected in JAVA stack.
Cheers..
Vasu
<i><u>** Reward Points if found useful **</u></i> -
No message in found in XI in IDOC to FILE scenario
Hi everybody,
I am working on a scenario idoc to file. The idoc is sent sucessfully from R/3 , but I am not getting any message in message monitoring in XI.Can anybody help me on this?Hi Bhagyashree,
Just see if the file is generated at the specified destination....
Meanwhile please go through the info below and cross check with what you have done...
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
I hope this answers your query.
Regards,
Abhy -
Error in Operation Mapping for Idoc to File Scenario
Hi Experts,
I am doing Idoc to File Scenario for Timesheet IDoc "HRSM_C" and following step are through,
Sender agreement --> Receiver Determination --> Interface Determination
got stuck in Operation mapping, it sahows error
"Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1"
Also not all the fields of IDoc HRSM_C are transferred to the XI server as I am unable to see all the fields in xml file using transaction idx5, as I suppose the reason behind may be there are no values in those fields.
Please suggest how to resove the issue and transfer all the fields from R3 to XI in Idoc eventhough it doesn't contain any value.Hi
Refresh CPA cache using user PIDIRUSER.
Look Note 951318 for Mapping Cache Refresh. -
Regarding IDOC 2 FILE Scenario
Hi Friends,
please help on IDOC 2 File Scenario. I have done tha ALE settings in R3 system and the Idoc has been generated out of r3 system. but how it wiil be sent to XI server can any body help me on this issue.make it as quick as possible.Hi,
Goto We02 and take the IDOC number froom there.
goto WE19, give the copied idoc number and click on execute.
Check for Control records for that IDOC and say outbound processing
ALE Settings
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Check this for posting the IDOC From R/3 to XI
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
/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
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI+--
StepsSummarized&
Regards
Seshagiri -
IDOC to FILE scenario With Screen shots
CAN YOU PLEASE SEND US THE DETAILS OF IDOC to FILE scenario With Screen shots and do the needful for me
Hi Surya,
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 helps.
Regards,
Abhy Thomas -
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.JainHi ,
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 .
Maybe you are looking for
-
HP LaserJet 400 color M451dw asking password to login
Hello, I purchased HP LaserJet 400 color M451 dw. after two months all the menu of this device disabled and it is asking password to login. i have in a big trouble. can anyone please help me how to reset this. i attached you the print screen. Thanks:
-
OK... I tried upgrading to Win XP 64-bit, but found there were games and applications that were screwy there and some items without 64-bit drivers, etc. So, I rolled back to a clean install of XP Home (32-bit). After much effort, I was told today at
-
Document Upload into Webdynpro and transfer to SAP R/3?
Hi Gurus, I have a requirement to offer a Document uploading option through Java webdynpro screen. I have referred the below link https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00062266-3aa9-2910-d485-f1088c3a4d71 which has the s
-
Export to Excel and File Upload is not working on ipad/IPhone
Hi We have a site in ASP.Net 2008 which is running on browsers and devices. There is an option to export to excel and file uploadd, It is working in the browsers but not working in Devices like IPad and Iphone. we are creating xml file when export to
-
Hi, I have been searching for a script ,that fetch the logged in time of all the users in a particular computer for a month.I couldnt find anything. Thanks in advance for quick response. Thanks and regards.. Midhun P s