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
Similar Messages
-
Error Resource not Found in SXMB_MONI while doing IDoc to File Scenario
Hi Experts,
I am doing IDoc to File Scenario and I am facing Following Error in SXMB_MONI,
<?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>Application</SAP:Category>
<SAP:Code area="MAPPING">RESOURCE_NOT_FOUND</SAP:Code>
<SAP:P1>193c0e01-bd37-11dd-850c-d879ac131b1f</SAP:P1>
<SAP:P2>http://clarityPOC</SAP:P2>
<SAP:P3>com/sap/xi/tf/_MM_Timesheets_iDocToFile_.class</SAP:P3>
<SAP:P4>-1</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>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</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have tested the same file in test tab of mapping, execution of mapping is successful there.
Regards,
Nitin Patil
Edited by: Nitin Patil on Dec 5, 2008 7:09 AMHi Dharmveer I have done the cache refresh ID in XI Data Cache Refresh using link
http://sapnbipoc:50000/rep/support/admin/index.html
but still same error persisting
and in Integration Builder> Environment>Cache Status Overview >Problem tab
following error (initial part of the error pasted) is shown
Thrown:
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Adapter Engine af.npi.sapnbipoc not found in SLD
at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:56)
at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:41)
at com.sap.aii.ib.server.abapcache.logons.IR_LogonData.<init>(IR_LogonData.java:26)
Regards,
Nitin Patil -
IDOC TO FILE Scenario - No Message arrive at PI
Hello,
i want to create a IDoc to File scenario. I already sent an IDoc from an ERP System to the PI.
The status text is ::000 and the information is 'IDoc sent to SAP system or external program'.
In the PI i have a Business System that shoud receive this IDoc but i can't find an incoming Message for example in the message monitor???
Somebody have an idea?
Thank you!Problem is solved.
I couldn't load the metadata for the IDoc, because their was no client in the RFC-Connection.
I haven't found this problem earlier, because the connection test was working well.
Anyway, thanks to all -
Context handling in message mapping for an IDoc to File Scenario
Hi,
Can somebody help me with this issue. I have an Idoc to file scenario. heres my idoc structure. Its a custom Idoc
Header (1..1)
Detail (0..Unbounded)
DependentDetail (0...Unbounded) Note: This dependentdetail is a subelement of Detail
Trailer(1...1)
I created my target structrure the same way as the Idoc structure.
My output is a simple text file. I need the output in this format
Header
Detail1
Dependentdetail1
DependentDetail2
DependentDetail3
Detail2
DependentDetail1
Dependentdetail2
Detail3
Detail4
Trailer
Since the Detail and Dependent Detail records are unbounded .
But right now i m getting my output like this:
Header
Detail1
Detail2
Detail3
Detail4
Trailer
But the DependentDetail record in not showing up in the output file. I didnot do any context change in my mapping. So do I need to do any context handling??...If so can somebody explain me with this.
Thanks,
Adam
Edited by: hymanroth on Apr 29, 2011 11:11 PMThanks Kenneth foryour quick reply,
Yes, I see the payload for Dependent detail in SXMB_MONI. So as you said earlier there's a problem with my content conversion.
my content conversion is as follows:
Header.fieldNames
Header.fieldFixedLengths
Header.endSeparator
Detail.fieldNames
Detail.fieldFixedLengths
Detail.endSeparator
DependentDetail.fieldNames
DependentDetail.fieldFixedLengths
DependentDetail.endSeparator
Trailer.fieldNames
Trailer.fieldFixedLengths
Trailer.endSeparator
So As I told earlier. With the above content conversion. I am not able to get the Dependent detail record in my output file. So If there is a change in my content conversion can u check it and tell me where I went wrong.
Thanks,
Harsh
Edited by: hymanroth on May 2, 2011 7:03 PM -
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 -
IDOC to File scenario Configuraton settings
hi,
I am doing IDOC to FILE scenario.I am sending IDOC from R/3 to XI and then to XML file.That mean smy scenario is as Follows ( R/3XIfile ) These are my queries
-->I have created RFC Destination from R/3 to XI.should I need to create RFC destination from XI to R/3 ( i mean In XI )??
-->I have created one Port in R/3 and I have linked that port with RFC Destination that i have created.here i am sending IDOC from R?# to XI...SO we call this PORT as SENDER PORT or RECEIVER PORT??
-->and DO we need to create PORT in XI also??is it require for my scenario??
-->DO we need to create Partner Profiles in XI also??
-->DO we need to create LOgical system in XI to represent the XI system?? (as we created LS in R/3 to represent sender system)
--->Here is my big doubt..
when we test IDOC ..by sing we19 TCODE,
We need to fill the corresponding details as below,
Receipent Sender
Port Port
PartnerNo PartnerNo
PartnerType PartnerType
my Doubt is,
-->>In which field we need to specify the Port that we have created in R/3..Receipent side OR Sender Side..?? and Why??
-->>Same for ParnerNo..where we need to specify the Logical system which we have created in R/3 should specify??Why??
Please give reply ASAP..with detailedexplanation..
points will be rewarded..
regards,
muraliHI
SLD-
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You donu2019t 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 will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You donu2019t 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 will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
/people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i
/people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD u2013 System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system names
cheers
reward poins if found useful -
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> -
Seeburger IDOC-to-File scenario: Error using Classifier module
Hello,
I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
localejbs/SeeClassifier classifier
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
classifier attID classifierAtt
classifier destSourceMsg MainDocument
classifier showInAuditLog true
bic classifierAttID classifierAtt
bic destEncoding UTF8
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName AUTO
bic newLine true
bic srcEncoding UTF8
After conversion in XI, the file fails to write to the folder because of this error:
Message processing failed. Cause: javax.resource.ResourceException: ---
Conversion of synchronous request from module chain ended with errors
---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
BICMapping Error: The mapping [not specified] you are trying to load cannot
be found in the right path! Maybe you forgot to compile or to activate the
mapping!
When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine. But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
I am only facing this problem for the IDOC-to-File scenario. Somehow the same configuration works for a File-to-IDOC scenario.
I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be. Has anyone encountered this problem before?
Any suggestions would be appreciated.
Thanks,
ArianneHi Yomesh,
Here is the payload.
<?xml version="1.0" encoding="UTF-8"?>
<LIST>
<S_ISA>
<D_I01>00</D_I01>
<D_I02/>
<D_I03>00</D_I03>
<D_I04/>
<D_I05>ZZ</D_I05>
<D_I06>CELORGS01</D_I06>
<D_I05_2>ZZ</D_I05_2>
<D_I07>AVX</D_I07>
<D_I08>032008</D_I08>
<D_I09>1718</D_I09>
<D_I10>X</D_I10>
<D_I11>00401</D_I11>
<D_I12>000000008</D_I12>
<D_I13>0</D_I13>
<D_I14>T</D_I14>
<D_I15>^</D_I15>
<S_GS>
<D_479>PO</D_479>
<D_142>CLS01</D_142>
<D_124>058895921</D_124>
<D_373>20080320</D_373>
<D_337>1718</D_337>
<D_28>8</D_28>
<D_455>X</D_455>
<D_480>004010</D_480>
<S_ST>
<D_143>850</D_143>
<D_329>800001</D_329>
<S_BEG>
<D_353>00</D_353>
<D_92>SA</D_92>
<D_324>4500005037</D_324>
<D_373>20051110</D_373>
</S_BEG>
<S_CUR>
<D_98>BY</D_98>
<D_100>USD</D_100>
</S_CUR>
<S_FOB>
<D_146>CC</D_146>
<D_309>OR</D_309>
<D_352>FREE CARRIER</D_352>
<D_334>02</D_334>
<D_335>FOB</D_335>
<D_309_2>DE</D_309_2>
</S_FOB>
<S_ITD>
<D_336>01</D_336>
<D_333>3</D_333>
<D_351>45</D_351>
</S_ITD>
<G_SN9>
<S_N9>
<D_128>L1</D_128>
<D_369>GEN</D_369>
<S_MSG>
<D_933>TEST</D_933>
</S_MSG>
<S_MSG>
<D_933>MESSAGE</D_933>
</S_MSG>
</S_N9>
</G_SN9>
<G_SN1>
<S_N1>
<D_98>BY</D_98>
<D_66>92</D_66>
<D_67>6310</D_67>
<S_PER>
<D_366>BD</D_366>
<D_93>Graham Crawford</D_93>
</S_PER>
</S_N1>
</G_SN1>
<G_SN1>
<S_N1>
<D_98>BT</D_98>
<D_66>92</D_66>
<D_67>6310</D_67>
</S_N1>
</G_SN1>
<G_SN1>
<S_N1>
<D_98>SE</D_98>
<D_93>3M COMPANY</D_93>
<D_66>92</D_66>
<D_67>0000019591</D_67>
</S_N1>
</G_SN1>
<G_SN1>
<S_N1>
<D_98>ST</D_98>
<D_93>SAMPLE</D_93>
<D_66>92</D_66>
<D_67>6310</D_67>
</S_N1>
</G_SN1>
<G_SPO1>
<S_PO1>
<D_350>00010</D_350>
<D_330>10.000</D_330>
<D_355>EA</D_355>
<D_212>10</D_212>
<D_639>PE</D_639>
<D_235>BP</D_235>
<D_234>230-1812-01JDS</D_234>
<D_235_2>EC</D_235_2>
<D_234_2>A00000000000002</D_234_2>
<G_SPID>
<S_PID>
<D_349>F</D_349>
<D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
</S_PID>
</G_SPID>
<S_REF>
<D_128>CO</D_128>
<D_127>4500005037-00010</D_127>
</S_REF>
<G_SSCH>
<S_SCH>
<D_380>10.000</D_380>
<D_355>EA</D_355>
<D_374>002</D_374>
<D_373>20051208</D_373>
</S_SCH>
</G_SSCH>
</S_PO1>
</G_SPO1>
<G_SCTT>
<S_CTT>
<D_354>1</D_354>
</S_CTT>
</G_SCTT>
<S_SE>
<D_96/>
<D_329>800001</D_329>
</S_SE>
</S_ST>
<S_GE>
<D_97>1</D_97>
<D_28>8</D_28>
</S_GE>
</S_GS>
<S_IEA>
<D_I16>1</D_I16>
<D_I12>000000008</D_I12>
</S_IEA>
</S_ISA>
</LIST>
Thanks,
Arianne -
Configuring IDOC to file Scenario in PI 7
Hello All,
I am doing an IDOC to file scenario, all the configuration is done. When i trigger the outbound IDOC, I can see in SXMB_MONI the sender component, sender Namespace, sender interface and reciever component are coming up correctly as configured.
1. But the reciever namespace and Reciever Interface are having the same values as the sender namespace and sender interface interface respectively. I am sure they have to be as per the config in ID.
2. Also on further going into the error message
SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code
SAP:AdditionalText>No standard agreement found for , DEV400, ANZ, BC_RECV_PAYM_ORD, urn:sap-com:document:sap:idoc:messages, PAYEXT.PEXR2002</SAP:AdditionalText>
Can anyone please suggest , what is it that I am doing wrong.
---PrashanthHi,
Please delete the Receiver determination and try creating again. refresh cache.
Can you please have a look at the sap notes if of any use .. i think its a different case altogether , but pls have a look.
SAP Notes 1278244- https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1278244
SAP Note 1284103 -https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1284103
Regards,
Srinivas -
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,
TirumalHi 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 -
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 AMDear 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. -
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 -
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,
SriniDear 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 ATTRIBUTE_INV_SND_SERV Error
Hi All,
I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>FILE_BC</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
Thanks,
GeethaThanks everybody! It has got fixed. I just requested No acknowledgements.
Geetha
Edited by: Geetha on Nov 11, 2009 5:45 PM
Maybe you are looking for
-
FireWire on Windows 7 (Boot Camp) don't work
Hi, I installed Windows 7 on a partition on my Mac (MacBook Pro retina, 15 inch, 2.6, 16 GB ram), for install cubase. I have a Audio Capture (Edriol FA-66), that connect to the computer with FireWire (I have also the Apple Thunderbolt to FireWire Ada
-
Shared iMovie 9.0 Project using iDVD option did not work
I created an iMovie project and want to create a DVD. I shared the iMovie project using the Share>iDVD option. The file took about 1-1/2 hours to create. Once it was completed iDVD opened but no movie appeared. I only saw the standard 4 option splash
-
Having problems opening an SSIS solution file
I have to make some changes to an SSIS package that was last modified in 2009 by a person who has left the company. I am having problems finding a version of Visual Studio that will open the SLN file. I do not know how the package was originally main
-
Hi, I've been experimenting with after effects lately, but am having a little trouble when bringing footage into FCP. When I bring footage in, it won't playback at normal speed in the viewer or the timeline, the footage jumps and won't play all the f
-
How to turn off 3g on Iphone 5 while keeping cellualar data on??
I have problem with this function on Iphone 5. I still want my iphone to receive email, imessage while keeping 3g mode off, as I don't subscribe for the unlimited package. However I found my iphone 5 still having 3g sign on permanently even I turn o