B2B Add on (Edi separator) IDOC AAE Receiver Error

Hi
We are getting an error, Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.engine.interfaces.messaging.api.exception.ConfigException: No sender agreement configured that matches the message's header fields (sender party: "xxxx", sender service: "", interface: "xxxx", receiver party: "", receiver service: "xxxx") when using IDOC_AAE Receiver adapter with ICO, scenarion works fine with standard IDOC adapter on integration engine
We have 7.31 dual stack with B2B addon sp03
We are using control records from mapping (reciver idoc adapter >advanced>control record in IDOC XML> all options selected)

Hi,
Yes, I filled the information on EDI separator channel, however this works fine with standard idco reciever adapter on integration engine, the issue is when I use ICO with Idoc_aae reciever adapter
you mean to say I have to use (.*) filling all sender edispeartor channel information mandatorily
what if I have to use the information to filter the message type from a multiple message type EDI file
Again this works absolutely fine with idco adapter on IE

Similar Messages

Error in IDoc AAE (Receiver) PI 7.3

Dear Experts,
I have a SOAP - IDoc scenario where I am using IDoc AAE reciver adapter for posting IDoc to SAP ECC system.
Message is successful in SXMB_MONI,however getting an error as below in receiver IDoc adapter.
Message processing failed. Cause: com.sap.aii.af.idoc.exception.IDOCAdapterException: com.sap.sql.log.OpenSQLException: Failed to set the parameter 9 of the statement >>INSERT INTO XI_IDOC_OUT_MSG ( IDOC_NUMBER , XI_MSG_NO , REF_NUMBER , ORIGINAL_IDOC_NO , IN_TIME , MESSAGING_TYPE , IDOC_TYPE , CIM_TYPE , SEND_PORT , SEND_PRTNR_NO , SEND_PRTNR_TYPE , CLIENT , STATUS , CONTROL_RECORD , CHANNEL_ID , ACK_NEEDED , ACK_RECEIVED , ARCHIVE ) values ( ?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,? ) <<: Cannot assign an empty string to a parameter with JDBC type >>VARCHAR<<.
My payload for this message is --
<HU_CREATE01>
               <IDOC BEGIN='1'>
                    <EDI_DC40 SEGMENT='1'>
                         <TABNAM>EDI_DC40</TABNAM>
                         <MANDT>120</MANDT>
                         <IDOCTYP>HU_CREATE01</IDOCTYP>
                         <MESTYP>HU_CREATE</MESTYP>
                         <SNDPOR>SAPPID</SNDPOR>
                         <SNDPRT>LS</SNDPRT>
                         <SNDPRN>BS_ORIWIN</SNDPRN>
                         <RCVPOR>SAPD3S</RCVPOR>
                         <RCVPRT>LS</RCVPRT>
                         <RCVPRN>D3SCLNT300</RCVPRN>
                    </EDI_DC40>
                    <E1BPHUHDRPROPOSAL SEGMENT='1'>
                         <HU_STATUS_INIT>A</HU_STATUS_INIT>
                         <PACK_MAT>000000000002001755</PACK_MAT>
                         <HU_EXID>00340042312419076037</HU_EXID>
                         <TOTAL_WGHT>11.123</TOTAL_WGHT>
                         <UNIT_OF_WT_ISO>KGM</UNIT_OF_WT_ISO>
                         <CONTENT>00002059911110071031</CONTENT>
                         <PLANT>9610</PLANT>
                         <STGE_LOC>2000</STGE_LOC>
                    </E1BPHUHDRPROPOSAL>
                    <E1BPHUITMPROPOSAL SEGMENT='1'>
                         <HU_ITEM_TYPE>1</HU_ITEM_TYPE>
                         <LOWER_LEVEL_EXID>00000000000000000000_Test</LOWER_LEVEL_EXID>
                         <PACK_QTY>12</PACK_QTY>
                         <BASE_UNIT_QTY_ISO>ZCP</BASE_UNIT_QTY_ISO>
                         <BASE_UNIT_QTY>ZCP</BASE_UNIT_QTY>
                         <MATERIAL>000000000000205991</MATERIAL>
                    </E1BPHUITMPROPOSAL>
               </IDOC>
          </HU_CREATE01>
Could you please give me your valuable input for the same.
Waiting for a reply.
Thanks in advance.
Best Regards,
Sugeet.

Hello
Note #1688780 IDoc AAE Adapter fails to insert empty strings in database, has been created to resolve this error. The fix is still being tested, so the note is not available for download just yet. Once the fix is released, the note will be available for download.
Here are some further details on the cause of the error:
The issue occurs if the persistency of the IDoc_AAE adapter is enabled
via the 'Persistance' property for the 'JavaIdocAdapter' resource
adapter and one or more of the IDoc relevant properties (for example
sender/receiver port, partner number or type) of the XI message is/are
empty strings. As empty string insertion into database is not supported
by the persictency framework the above OpenSQLException exception is
thrown and the XI message processing fails.
Regards
Mark

B2B add-on

Hi,
We all know that B2B scenario involves Party to Party communication as the systems involved
in message exchange are in different landscapes.We also checkbox for sender uses virtual receiver
while creating receiver determination.
We have one B2B scenario where (EDI to IDoc-XML) parties are not used.
Does B2B add on eliminates the need for party to party comunication?
Regards,
Mayank Yadav

Thanks All for Help,
Actually in my scenario B2B add on was installed and Parties were not used.
So I got confused why Party is nt used here since its a B2B.
Now I got a clear idea about B2B addon- it converts EDI to EDI-XML
just like Seeburger BIC mapping Designer does for Seeburger AS2 adapter.
Morever Party was not used here(in my B2B scenario where B2B add on was installed;business component is used instead of Business system) because 1 sender and 1 receiver system is there.
Party will be used only when we have multiple external sender/receiver systems across the landscape so that they can be identified with globally valid IDs.

SAP PO EDI Separator Channel Error

Hi All,
We have an Inbound EDI(INVOIC D01B format) Interface. There are 2 flows involved for the same.
1 st flow: File -> EDI Separator
2nd flow: EDI Separator -> IDOC
Sometimes its successful in the 1st flow and In the 2nd flow it picks different channel (Since we have 5 more EDI separator sender channels) and its throwing a mapping error since it picks different format.
In receiver EDI separator channel we are getting the error.EDI Separator channels behaves differently each time.
When same file is tested in B2B cockpit its Successful. So I am guessing no issues with the file used for testing.
We have tried below options:
We did a Full Cache refresh and tested again still the same error exists.
Stopped all other sender EDI Separator channel and tested still same error exists.
Tried to keep only 1 sender EDI Separator channel and tested still same error exists.
Tried a dummy change to all channels and tested again still same error exists.
Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'ba6bc28e205c33629ec6d1cb5e2fb164': Catching exception calling messaging system
MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'ba6bc28e205c33629ec6d1cb5e2fb164': Catching exception calling messaging system
Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'ba6bc28e205c33629ec6d1cb5e2fb164': Catching exception calling messaging system
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'ba6bc28e205c33629ec6d1cb5e2fb164': Catching exception calling messaging system
Please let me know your Suggestions if any!
Appreciate your help!
Thanks,
Sharanya

Hi Dimitri,
I have tried giving all the parameters like Message type,Version....etc..
But still it doesn't work.
Thanks,
Sharanya

Sap pi b2b add-on

Hello
We are currently planning on getting on SAP PI B2B ADD-ON. Currently we generate the EDI formatted file using file content conversion in the receiver file adapter. It is a very laborious task.
Does getting the B2B ADD-ON eliminate the file content conversion to produce the EDI file format ? Also how much time would cost would be saved if we got the b2b ADD-ON? Is there anyone who is doing file content conversion to generate the edi file format ? What are your thoughts?
Thanks!

Hi ,
Go through below link.
The SAP PI B2B add-on EDI capabilities unveiled
Regards
Venkat

Classifier mapping to read Sender & Receiver Identification Number from XML. How to handle in B2B Add on

In current See burger tool, We have this functionality to read Sender and Receiver Identification number from the XML. Is there any way in b2b add on to do this.

Hi,
The classifier within the Seeburger context is being used to call your parent mapping, in case you want to dynamically determine your mapping, based on data in the UNB/UNH segment.
Within the B2B add-on, there is no need to.
Only use module localejbs/EdifactConverterModule in case you want to convert to or from EDI.
You have a specific requirement or do you want to test something out?
Kind regards,
Dimitri

IDoc Receiver, Error in we02 - EDI: Partner profile inbound not available

Hi All,
I have a problem when creating a receiver IDoc from XI to R/3.
I have successfully tested the IDoc when populating the receiver information from the payload. However I want this information to be populated automatically based on the logical systems.
When I do this I get the following error in the IDoc in R/3:
EDI: Partner profile inbound not available
In the control record the sender information is all correct but in the recipient information the partner Number with type LS is populated, but port is not populated.
I have done the following steps.
     the sender is a Business Service so I have created a logical system directly adapter-specific identifiers in the sender service in the integration directory.
     In the receiver business system I have imported the logical system into the adapter-specific identifiers in the ID from that specified in the SLD.
     In the receiving R/3 system using SALE/BD54 I have created a logical system for the source system.
     In the receiving R/3 system using we20 I have created a partner profile of type LS with the same name as the source logical system.
     IN PI/XI system in transaction IDX1 Ive created a port (SAP<SID> where <SID> is the system ID of the receiving R/3 system) and the client of the R/3 system, and the RFC destination of that system (<SID>CLNT<clnt>, as specified in SM59).
     In the IDOC Adapter (receiver) I have entered the RFC destination and port matching those created above. All checkboxes are UN-checked eg. take sender from payload, take receiver from payload, Apply control record values from payload, etc. are all NOT checked.
I think that Ive done everything correctly, but I get the error in we02 in R/3: EDI: Partner profile inbound not available.
Any help will be greatly appreciated (and rewarded, obviously).
Thanks,
Matt.

HI Matt,
Can you please copy paste the exact error message....In your error message it will show you Exact partner Number / Logical System name and other parameters...just compared if you have all parameters set in your partner profile comparing to error message...
If you can giev screen shot of both..then probably would be easy to point out error.
Hope this will help.
Nilesh

B2B Add on - Accepted /Partially Accepted using EDI Seperator.

I want to configure this feature of Accepted /Partially Accepted using EDI Seperator.
We were using seeburger Adapter and could configure this.
The scenario is :
When multiple EDI files is being processed in an inbound scenario using EDI separator Channel. , If any files fails due to Data /syntax error,
How to identify which file is been failed and how to send error ackn back to sender mentioning the files failed. .
Please can anyone help me on this.

Hi,
If I'm not mistaken, this feature is available as of SP3.
Ruchir Sinha, please correct me if I'm wrong.
Kind regards,
Dimitri

Comparison between split Adapter in Seeburger and EDI Separator

Hello All,
Currently we are designing EDI interfaces using B2B Add-On.
I am trying to compare the split Adapter of Seeburger and EDI Separator of B2B Add-on.
In Seeburger Splitter configuration:
The additional split configuration helps to map the Sender ID, (EDIType,Transaction,Version) combination to split channel and sender agreement.
I believe a List of Sender Id, Mappings (Standard, Transaction, Version) combinations can be added to the same Split channel and Sender Agreements.
In B2B Add-On:
The sender ids , EDI details are directly mentioned in the channel and it is bound to sender agreement.
Does it reduce the flexibility in EDI Scenarios.Is that a correct point of view?
Your inputs highly appreciated.
Thanks.
Regards,
Sudharshan N A

Dear Sudharshan,
yes, I would say that this is a correct point/observation. When the Seeburger Adapters were introduced many years ago, one focus was put on the flexibility by keeping all functionality related to the "format conversion" (Classifier/Bic/Splitter) completely separated from the "data transmission" functionality directly in the channel.
This way, the format conversion modules could be included in any adapter that was running on the AdapterEngine and not just to the See-Adapters.
In a typical setup on client side, almost all inbound channels were using the "AUTO" functionality to detect all required parameters to select the right Split-Channel...so all channels had the same module-chains included (no matter if it was an AS2-Channel or a simple FILE/FTP-channel.
This also allowed for easy reprocessing of any received file (via AS2, X400 , OFTP or else....) by just putting the file again to a file-channel with the same module-chain parameters.
Kind Regards
Stefan
Btw... I am not very familiar with the B2B AddOn, but if you have additional questions regarding the Seeburger-EDI-Adapters, feel free to ask...

Query on EDI Separator adapter

Hi,
We are using B2B Add-On and EDI Separator adapter.
There is a EDIFACT interface handling a particular transaction and version - Orders D96A. For a bunch of the partners (sender/receiver id combinations) we need to invoke a particular mapping and rest of the partners to use a different mapping.
How can this be accomplished?
Regards
Rizwana

Hi Piyush,
I have created one EDI separator channel as Sender Id as *,and one more EDI separator channel with specific Partner sender ID eg "123456".
When an EDI file for specific partner 123456 arrives it invokes both the default and specific channels and flow.
Is this a bug or expected behavior of the EDI Separator sender channel.
Regards
Rizwana.

Reg XML to Plain Conversion using B2B add on

Hi All,
This is an outbound scenario where the message is sent to AS2 receiver channel and the output is Plain file. I have added all the module parameters
and the content type as application/plain. While testing I am facing the error,
Exception caught by adapter framework: XML-Parser error occured while parsing: Cannot initialize XML to plain handlerCan not find a matching configuration for sender party "", service , receiver party ,service , namespace , action in table B2B_PLA_CTRL_IF.
Can anyone help me on this issue.
Cheers,
Neethu

Hi Neethu,
Did you import the content? See How to install the new B2B add-on , see step 5.1
You need to do this for the message type you want to exchange ((EDI, ansi X.12, ...).
Also, please do step 5.2. I guess this is not the case.
Kind regards,
Dimitri

In EDI to IDOC or Idoc to EDI can we go for Dynamic recevier determination

Hi all
I am doing an EDI to IDOC scenario involving SEEBURGER( AS2) adapter .can we go for extended receiver determination
Regars
Saurabh

Saurabh,
You can not use Extended Receiver Determination coz AS2 connection is like point-to-point connection which requires AS2 id of both sender and receiver. Therefore you can not use the Extended receiver determination.
Reagrds,
Sarvesh

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

SAP ERP - SAP ME - iDOCS - Not received

Dear Experts,
We are trying to send data ( MATMAS iDOC) from ERP to ME.
We used the below transaction in SAP.
1. using BD10 transaction in SAP ( Send material) Idoc was sent
Checks :
We checked in WE05 in SAP and found that Idocs sent is successful
Opened MII ( Queue Monitor) and Found that Idoc was received successfully with ID but Message ( "" sucessfully Queued) Status : Queued
Problem : We are not able to see the material in ME system
No errors found in NWA logs.
Kindly suggest any solution.
Regards
Shankar

Make sure you have the plant id in the idoc. Here are the few place in the idoc that you need to add the PlantID. We're using TN01 as our plant.
<MATMAS03>/ <IDOC>/ <E1MARCM>/ <WERKS>TN01</WERKS>
<MATMAS03>/ <IDOC>/ <E1MBEWM>/ <BWKEY>TN01</BWKEY>
<MATMAS03>/ <IDOC>/ <E1MVKEM>/ <DWERK>TN01</DWERK>

Regarding EDI----XI----IDOC

Hi All,
I have One Requirement here is that
My Client's Customer will send EDI Formated Data (ANSI Type ) to Client. That Data has to be Posted into SAP R/3 Database. So here We are Using XI For that .
Can Any One Explain me what could be the Scenario here And
How to Handle this ANSI Data Format.
Regards
Babu

Hi
Scenario is EDI-XI-IDOC
Data Will come in the Form of ANSI
1) I Will Use IDOC Adapter in the Receiver End
2) For Sender Side Which Adapter I Need to Use & How to do the Conversion From ANSI Format to XML ??????
Can You Provide Any Real time Scenario Or Any thing Which meets this Requirement.
I am Still in Confusion How this ANSI Data Will be Converted into XML Either it Can Happen in Seburger Adapter OR in XI Also
Can You Expalin me How this Conversion in Detailed
>>>>>>>>>>>>>>>>
if you are getting the data in the format like ANSI then you have to first create the XML message with the help of the BIC mapper.
the BIC mapper is basically used to convert the EDI message into the XML message. to convert the EDI message into XML message ypu have to create the mapping using the option createE2xmapping in the BIC mapper.
the mapping that will be generated using the BIC mapper have to be deployed on the server.
and in the adapter you have to used the same mapping name that you have deploy on the XI server in the module tab of the adapter.
if you still face the problem please reply me back.
Thanks
Rinku

B2B Add on (Edi separator) IDOC AAE Receiver Error

Similar Messages

Maybe you are looking for