EDI Inbound Interface

Dear Friends,
In our organization, there is a third party involved into stocktake and provide us input flat files for each plant separately. These files are loaded into SAP automatically as iDoc, this is working good.
Some details of EDI configuration are
Partner Type KU: (Each Plant is being configured as a customer Partner Type KU)
Inbound Parameter, Message Type : WVINVE
Process Code: WVIN
Identification: IDOC_INPUT_STORE_INVENTORY
Option ALE: Radio Button "Processing with ALE Services"
Processing Type: Radio Button "Processing by function module"
I am trying to find out where is these automation done? (I mean how incoming data is being loaded into sap automatically?)
and where(directly etc) initially incoming data is being stored into SAP?
Regards,
Sunny

Hi,
IDocs are nothing more than structured ASCII data, you could always process them directly with an ABAP. This is certainly the quick and dirty solution, bypassing all the internal checks and processing mechanisms. We will not reinvent the wheel here..
Please check the below link...
http://www.idocs.de/www5/EDI/HTML/IDocBook.htm#_Toc8400370
Hope it may help you.
Kuber

Similar Messages

Duplication of invoice from EDI Inbound interface

Frnds
we are receiving EDI invoices form one of the vendor, so he just sends a file of the invoice and it get posted in SAP
But the issue is that for one invoie,two invoices are generated with all the same inforamtion.
I mean one invoice is poste 10000 and another invoice 10001 will be posted with the same informaiton which is posted in 10000, even reference number remains the same.
why it is happening, shouldnt SAP stop the duplicate invoice entry?
under vendor master record, Duplicate invoice indiacator is ON
please let me know any input

Hello,
Please check under configuration Duplicate invoice check is activated for your company code
Materials Management>Logistics Invoice Verification>Incoming Invoice -->Set Check for Duplicate Invoices
Also Please check the Message number M8 108 should set as error, to prevent the posting of invoice , in standard system this is information message only
Thnaks & Regards,
Sridhar.G

EDI : inbound processing error.

Hi All,
I am facing the below error
"Entry in inbound table not found" status 56.
I am setting a new EDI inbound interface for goods reciept GR:
We have got a flat file which we are trying to upload from SAP directory.
after uploading i am getting the above error. The error points at Partner Profile details stating the details doesnot exist. But i cross checked and its all correct.
- Partner Profile created.
- Message type exixt in INBOUND Parameters.
If i reprocess this failed idoc using we19 selecting INbound function module "L_IDOC_INPUT_WMMBXY" then it gets processed successfully.
If i reprocess this failed idoc via editing and then running report RBDINPUT for processing edited idoc status 69, then the probelm persist.
I dont know what i am missing.
Thanks in advance.

Hi,
I am getting the same error.
Can u please help me on this.
Thanks and Regards
Neha Kapoor

EDI Inbound ( need code sample )

Hi Guus,
 I have an object to develop , its and EDI inbound interface . Can some one send me sample code or atleast guide me from where I can start.
Regards
Avi.......

Hi ,
plz go through the below code..
FUNCTION zsd_idoc_input_order_change.
""Local Interface:
*" IMPORTING
*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*" VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*" REFERENCE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*" REFERENCE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*" REFERENCE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*" REFERENCE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*" IDOC_CONTRL STRUCTURE EDIDC
*" IDOC_DATA STRUCTURE EDIDD
*" IDOC_STATUS STRUCTURE BDIDOCSTAT
*" RETURN_VARIABLES STRUCTURE BDWFRETVAR
*" SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*" WRONG_FUNCTION_CALLED
Work areas for the idoc tables.
DATA: wa_data TYPE edidd.
status = '53'. "initial
Read the control data information of idoc.
READ TABLE idoc_contrl INTO gwa_control WITH KEY mestyp = 'ZORDRPLY'.
IF sy-subrc EQ 0.
Extract the data from the segments.
 LOOP AT idoc_data INTO wa_data "LOOP AT idoc_data
 WHERE docnum = idoc_contrl-docnum.
 CASE wa_data-segnam. " CASE gwa_data-segnam
 WHEN 'Z1SCSK'. "Header data
 MOVE wa_data-sdata TO gwa_z1scsk.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = gwa_z1scsk
 IMPORTING
 output = gv_vbeln.
 WHEN 'Z1SCSP'. "Item data
 MOVE wa_data-sdata TO gwa_z1scsp.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = gwa_z1scsp-posnr
 IMPORTING
 output = gv_posnr.
 gwa_z1scsp-posnr = gv_posnr.
 APPEND gwa_z1scsp TO i_z1scsp.
 ENDCASE. " CASE gwa_data-segnam
 ENDLOOP. "LOOP AT idoc_data
Update the sales order
 PERFORM order_change.
ELSE.
Begin of Mod-001
 status = '51'.
 bapi_retn_info-type = 'E'.
 bapi_retn_info-id = 'ZSDM'.
 bapi_retn_info-number = '028'.
 bapi_retn_info-message_v1 = 'Wrong'.
 bapi_retn_info-message_v2 = 'Message'.
 bapi_retn_info-message_v3 = 'Type'.
 RAISE wrong_function_called.
ENDIF. " IF sy-subrc EQ 0
*Start wf
PERFORM wf_start
 USING
 idoc_contrl-docnum
 gv_vbeln
 CHANGING
 bapi_retn_info.
*end of starting of wf
*set status
IF status = '53'.
 bapi_retn_info-type = 'S'.
 bapi_retn_info-id = 'ZSDM'.
 bapi_retn_info-number = '028'.
 bapi_retn_info-message_v1 = gv_vbeln.
 bapi_retn_info-message_v2 = 'Changed.'.
 bapi_retn_info-message_v3 = 'Succcessfully'.
ENDIF.
PERFORM idoc_status_ord_change
 TABLES idoc_data
 idoc_status
 return_variables
 USING idoc_contrl
 bapi_retn_info
 status
 workflow_result.
End of Mod-001
ENDFUNCTION.
FORM idoc_status_ord_change
 TABLES idoc_data STRUCTURE edidd
 idoc_status STRUCTURE bdidocstat
 r_variables STRUCTURE bdwfretvar
 USING idoc_contrl LIKE edidc
 value(retn_info) LIKE bapiret2
 status LIKE bdidocstat-status
 wf_result LIKE bdwf_param-result.
CLEAR idoc_status.
idoc_status-docnum = idoc_contrl-docnum.
idoc_status-msgty = retn_info-type.
idoc_status-msgid = retn_info-id.
idoc_status-msgno = retn_info-number.
idoc_status-appl_log = retn_info-log_no.
idoc_status-msgv1 = retn_info-message_v1.
idoc_status-msgv2 = retn_info-message_v2.
idoc_status-msgv3 = retn_info-message_v3.
idoc_status-msgv4 = retn_info-message_v4.
idoc_status-repid = sy-repid.
idoc_status-status = status.
APPEND idoc_status.
IF idoc_status-status = '51'.
 wf_result = '99999'.
 r_variables-wf_param = 'Error_IDOCs'.
 r_variables-doc_number = idoc_contrl-docnum.
 READ TABLE r_variables FROM r_variables.
 IF sy-subrc <> 0.
 APPEND r_variables.
 ENDIF.
ELSEIF idoc_status-status = '53'.
 CLEAR wf_result.
 r_variables-wf_param = 'Processed_IDOCs'.
 r_variables-doc_number = idoc_contrl-docnum.
 READ TABLE r_variables FROM r_variables.
 IF sy-subrc <> 0.
 APPEND r_variables.
 ENDIF.
ENDIF.
ENDFORM. "idoc_status_ord_change
***INCLUDE LZSD_FS007_ORDERCHANGEF01 .
*& Form order_change
 This Form is used for updating the DB tables(vbap,vbep) *
FORM order_change .
Declaration of internal tables.
DATA : i_vbap TYPE STANDARD TABLE OF vbap,
 i_vbep TYPE STANDARD TABLE OF vbep.
Declaration of workareas.
DATA : wa_vbap TYPE vbap,
 wa_vbep TYPE vbep.
Declaration of constants.
CONSTANTS : lc_sno(3) TYPE c VALUE '039',
 lc_ino(3) TYPE c VALUE '040',
 lc_msg(4) TYPE c VALUE 'ZSD',
 lc_emsgty(1) TYPE c VALUE 'E',
 lc_smsgty(1) TYPE c VALUE 'S',
 lc_estatus(2) TYPE c VALUE '51',
 lc_sstatus(2) TYPE c VALUE '53'.
Declaration of variable.
DATA : lv_index TYPE syindex,
 lv_zzproddt TYPE sydatum.
Fetch the data from vbap
SELECT * FROM vbap INTO TABLE i_vbap
WHERE vbeln EQ gv_vbeln.
IF NOT i_vbap IS INITIAL.
Fetch the data from vbep
 SELECT * FROM vbep INTO TABLE i_vbep
 FOR ALL ENTRIES IN i_vbap
 WHERE vbeln EQ i_vbap-vbeln
 AND posnr EQ i_vbap-posnr.
Modify production option date (zzproopdt) of i_vbap
and production date(zzproddt) & original production date(zzoprodt)
of i_vbep with the data sent by SCS.
 lv_index = 1.
 LOOP AT i_z1scsp INTO gwa_z1scsp.
 LOOP AT i_vbap INTO wa_vbap WHERE posnr = gwa_z1scsp-posnr.
 IF sy-subrc EQ 0 .
Copies the date value in gwa_z1scsp-zzproopdt to wa_vbap-zzproopdt,
if valid date is there in gwa_z1scsp-zzproopdt
 PERFORM validate_date USING gwa_z1scsp-zzproopdt
 wa_vbap-zzproopdt.
 IF NOT wa_vbap-zzproopdt IS INITIAL.
 MODIFY i_vbap FROM wa_vbap TRANSPORTING zzproopdt.
 ENDIF.
Copies the date value in gwa_z1scsp-zzproddt to lv_zzproddt,
if valid date is there in gwa_z1scsp-zzproddt
 PERFORM validate_date USING gwa_z1scsp-zzproddt
 lv_zzproddt.
If gwa_z1scsp-zzproddt is not initial then only update in VBEP.
 IF NOT lv_zzproddt IS INITIAL.
 LOOP AT i_vbep INTO wa_vbep FROM lv_index.
 IF wa_vbep-posnr GT wa_vbap-posnr.
 lv_index = sy-tabix.
 EXIT.
 ELSEIF wa_vbep-posnr EQ wa_vbap-posnr.
 wa_vbep-zzproddt = lv_zzproddt.
 Update Original Production date only when its initial.
 IF wa_vbep-zzoprodt IS INITIAL.
 wa_vbep-zzoprodt = wa_vbep-zzproddt.
 ENDIF.
 MODIFY i_vbep FROM wa_vbep TRANSPORTING zzproddt zzoprodt.
 ENDIF.
 CLEAR wa_vbep.
 ENDLOOP.
 ENDIF.
 ELSE.
Begin of Mod-001
 status = lc_estatus.
 bapi_retn_info-type = lc_emsgty.
 bapi_retn_info-id = lc_msg.
 bapi_retn_info-number = lc_ino.
 bapi_retn_info-message_v1 = gwa_z1scsp-posnr.
 ENDIF.
 ENDLOOP.
 IF sy-subrc EQ 4.
 status = lc_estatus.
 bapi_retn_info-type = lc_emsgty.
 bapi_retn_info-id = lc_msg.
 bapi_retn_info-number = lc_ino.
 bapi_retn_info-message_v1 = gwa_z1scsp-posnr.
 ENDIF.
 CLEAR: wa_vbap, gwa_z1scsp.
 ENDLOOP.
ELSE.
 status = lc_estatus.
 bapi_retn_info-type = lc_emsgty.
 bapi_retn_info-id = lc_msg.
 bapi_retn_info-number = lc_sno.
 bapi_retn_info-message_v1 = gv_vbeln.
 EXIT.
End of Mod-001
ENDIF.
Update the DB tables
 UPDATE vbap FROM TABLE i_vbap.
 UPDATE vbep FROM TABLE i_vbep.
ENDFORM. " order_change
*& Form VALIDATE_DATE
Converts the date into DATS format and check if it is valid,
if valid returns date in p_date_dats else clear it.
 -->p_date_c8 Date in Char format send by SCS
 -->p_date_dats Date in DATS format.
FORM validate_date USING p_date_c8 TYPE char8
 p_date_dats TYPE dats.
CLEAR p_date_dats.
p_date_dats = p_date_c8.
CALL FUNCTION 'DATE_CHECK_PLAUSIBILITY'
 EXPORTING
 date = p_date_dats
 EXCEPTIONS
 plausibility_check_failed = 1
 OTHERS = 2.
check sy-subrc NE 0.
 CLEAR p_date_dats.
ENDFORM. " VALIDATE_DATE
*& Form wf_start
 text
 -->P_IDOC_CONTROL_DOCNUM text
 -->P_GV_VBELN text
 <--P_BAPI_RETN_INFO text
FORM wf_start USING p_idoc_control_docnum
 p_gv_vbeln
 CHANGING p_bapi_retn_info TYPE bapiret2.
INCLUDE <cntn01>.
DATA: agents LIKE swhactor OCCURS 1 WITH HEADER LINE,
 process_type TYPE char1,
 idoc_no TYPE edidc-docnum,
 creator LIKE swwwihead-wi_creator.
swc_container wi_container.
swc_create_container wi_container.
swc_set_element wi_container 'Document_no' p_gv_vbeln.
swc_set_element wi_container 'Process_type' '1'.
swc_set_element wi_container 'Idoc_no' p_idoc_control_docnum.
CALL FUNCTION 'SWW_WI_START_SIMPLE'
 EXPORTING
 creator = creator
 task = 'WS90200019'
 TABLES
 agents = agents
 wi_container = wi_container
 EXCEPTIONS
 id_not_created = 1
 read_failed = 2
 immediate_start_not_possible = 3
 execution_failed = 4
 invalid_status = 5
 OTHERS = 6.
IF sy-subrc <> 0.
 p_bapi_retn_info-type = 'E'.
 p_bapi_retn_info-id = sy-msgid.
 p_bapi_retn_info-number = sy-msgno.
 p_bapi_retn_info-message_v1 = sy-msgv1.
 p_bapi_retn_info-message_v2 = sy-msgv2.
 p_bapi_retn_info-message_v3 = sy-msgv3.
 p_bapi_retn_info-message_v4 = sy-msgv4.
ENDIF.
ENDFORM. " wf_start..
The idoc configurations for customized idoc (inbound) are..
1>WE81
2>WE31
3>WE30
4>BD51(Attach ur zfunction mdoule)
5>WE57(Attach ur zfunction mdoule to message type and basic type)
6>we42
7>WE20...
Regards,
nagaraj

Inbound Interface for Accepting Bank Statement Through EDI

Hi All ,
Pls Help me out to complete this Scenerio with u r Ideas and Inputs .
Inbound Interface for Accepting Bank Statement Through EDI.
Rgds
Rafi .

Hi,
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training

How to connect to third party using PI for outbound and inbound interfaces

Hello,
I have scenarios where I have data coming in from third party EDI subsystem and sent to SAP. And also from SAP to EDI subsystem. We need to send the XMLs to the EDI subsystema nd also receive XMLs.
Can someone please suggest the ways I can connect to EDI subsytem for both Outbound and Inbound interfaces.
Thanks

Hi Prabhu,
EDI file is different from the normal flat or xml file. Hope you understand the difference.
Now if your EDI subsytem has the capability of converting the xml file to edi file viceversa then create and receive the xml file from the EDI subsystem. For the xml file you may use the file adapter as an option.
If it doesnot have the capability then seeburger adapter needs to be used. This is not an inbuilt adapter. So your company needs to purchase it.
Regards,
---Satish

Inbound interface was found more than once

Hi All,
Currently I'm working on a scenario wherein an invoice file is generated and created on FTP server, PI system picks up invoice (xml file) and sends to customer via EDI 810. The scenario failed in sxmb_moni and below is the error message.
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
<SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xyz:sap:components. 810_Outbound_Async_MI</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the inbound interface: Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xyz:sap:components. 810_Outbound_Async_MI Inbound interface was found more than once (for same sender and receiver) for outbound interface
Can anyone help me out and provide some valuable suggestions.
Regards
Faisal

Hi Abdul,
Try to run the scenario in the ID.
There is one test tool to in directory for this, login to ID --> go to Tools --> Test configuration.
This will show you the error in the exact step.
-Supriya.

Multi-mapping for EDI 810 Interface

Hi,
I am building EDI 810 interface. We have following requirements.
Source system is SAP. Target systems is AAFES and COSTCO.
1 Source system and 2 target System.
For example: Can i have Interface mapping as shown below?
Invoice IDoc -> MM_EDI_810_AAFES -> EDI_810
MM_EDI_810_COSTCO
Based on DUNS number can i re-direct the interface to choose one of the mapping and accordingly choose the communication channel?
Thanks,
Gowri

Hi,
You can do this in any of the following ways:
Content based routing in XI can be done during
1) Receiver Determinations (Integration Directory) --- Used for entering a condition for
forwarding a message to one or more receivers
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
2)Interface Determinations (Integration Directory) --- Used for entering a condition for forwarding a message to multiple inbound interfaces
3) Designing Integration Processes (ccBPM) (Integration Repository) --- Used for entering a condition for processing process steps (see Step Types)
At all the 3 places u will use the Condition editor,
http://help.sap.com/saphelp_nw04/helpdata/en/67/49767669963545a071a190b77a9a23/content.htm
Hope this helps you.
Regards,
Abhy

File name with latest time stamp for inbound interface

Hi experts,
I have a requirement to develop an inbound interface in which I need to fetch the all files from the physical directory, and then retrieve the one with the latest timestamp. I found out the FM 'SUBST_GET_FILE_LIST', but this FM does not gives me the timestamp.
Is there any other FM/table through which this can be achieved?
Thanks,
Mohit.

Can you please try with these functionmodules???
1)ITS_DIRECTORY_LIST_FILES
2)CL_GUI_FRONTEND_SERVICES=>DIRECTORY_LIST_FILES

Need information on how to create Idoc Inbound Interfaces for Business Sys

Hi,
I'm losing it.
Can anyone point me to some documentation or an example of how to create inbound interfaces for Business Systems in PI 7.1.
Here's the scenario
I'm working on a B2B integration process which sends inbound idocs to an ECC 6.0 system.
I've created the Business System communication component but under the Inbound Interfaces it is blank.
I want to have MBGMCR.MGBMCR03 as an inbound interface.
But I forget how to get it there.
For Business components you can just add the inbound interface.
I've already defined the Business System in the SLD pointed it to the correct Tech System, imported the idoc definitions in the Enterprise Service Builder and set up IDX1, IDX2 to ensure the metadata exists in PI.
But for Business systems the hep says that it's got to come from the SLD.
Outbound/Inbound Interfaces
For each business system, the interfaces that are installed on the business system are also entered in the SLD. These interfaces are displayed in this frame. You cannot add any other interfaces.
I know I've done this before, but I can't remember how.
Cheers,
John

Hi John ,
Please have a look at the following links which might be of help to you
PI 7.1 IDocs interfaces act as operations
http://www.sdn.sap.com/irj/scn/weblogs;?blog=/pub/wlg/7933
/people/peter.gutsche/blog/2008/10/27/what146s-new-in-sap-netweaver-pi-71
There is a section in the following link on IDOC , have a look at the links in that section
https://wiki.sdn.sap.com/wiki/display/XI/ImportantBlogsand+Notes
Best Regards

Read EDI-856 interface data in ABAP program

HI Experts,
I have a requirement to read the incomming EDI-856 interface data from ABAP program and generate an IDOC. I have gone through few EDI-856 documents and theformat in which to read the data .
Request you to let me know the code logic , function module to use or if you have any document which can help me in the development.
Thanks in advance
Regards
Santosh

Please help regarding
First could you please help me regarding the SCN search option?
please always try to attempt from your side if not able to solve than search in SDN finally you may land on SDN with thread.

Error when trying multiple inbound interface determination for IDOC

Hi !
I have this scenario: File -> XI -> IDOC.
For each source file, I need to send multiple idoc packages, all to the same business system, but each package should be the result of different interface mappings.
All mappings have same source and target message types...e.g. source: MT_MyFile, target: CREMAS04.
To avoid creating a generic mapping program, we need to duplicate the current mapping program, make it handle the new case, and then add it as second interface mapping in Interface Determination, with same inbound interface, but different interface mapping, without conditions. All interface mapping should execute.
We are receving this error:
<SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
<SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:P1>
<SAP:Stack>Error when determining the inbound interface: Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:Stack>
Any clues?
Regards,
Matias.

Hi Satish !
Thanks.
I need to send different IDOCs to SAME business system.
In Interface determination I need this:
Inbound Interface -
Condition -
Interface Mapping
IF_1 no condition M_1
IF_1 no condition M_2
I need to send BOTH IDOC packages to same business system.
But it keeps throwing the posted error.
Regards,
Matias.

How to handle multiple inbound interfaces with WSDL messages

Hi All,
We have a synchronous: Abap Proxy -> XI -> WebService Scenario. The webservice has multiple SoapActions e.g. SearchForProduct_WithX, SearchForProduct_WithY each with different message types. We have tried to use the receiver determination to send the request to the correct soapaction using conditions e.g. if field X in the request is populated use SearchForProduct_WithX action/message.
But when we run it through the proxy we get this error:
<CODE>IF_DETERMINATION.TOO_MANY_IIFS_CASE_BE</CODE>
<ERRORTEXT>Multiple inbound interfaces not supported for synchronous calls</ERRORTEXT>
Does anybody know how we can get around this or how best to deal with the multiple soap actions per wsdl situation.

Hi Yaghya,
We have used conditions in the Interface Determination. Interestingly if we use an HTTP sender adapter we can use this configuration ... but once we try and use ABAP proxies we get the previous error.
Another related question ... when we use the http adapter we get a connection time out exception. Same thing happens if we try and use the wsdl tester at /wsnavigator but we can open the wsdl through the browser. Any idea on this one?
Thanks for all your help.

EDI Inbound-Port definition

Hi,
We are doing EDI Inbound for PO. For this I need to define the port(Sender Port) as in the control record(i.e as they r sending) .If they change their port it is not working what shold I do for this.
regds,
Vinsa.R

Hi,
As i mentioned before, the sender should inform any change in control parameter so you can change your port too.
Check with the sender if they can provide this information before changing. I do not what is the terms of your company with this sender, but they should inform you before doing any change.
Option-2
The other option you have is, you create your custom program which runs before RSEINB00. In this program you have to,
- read each and every file from this UNIX directory
- read the control record.
- check if SNDPOR is what you have defined in your system
- if not then change it and save it back.
You can check the source code of FM 'IDOC_INBOUND_FROM_FILE' to see how SAP read this file. ( Program RSEINB00 calls this FM internally ). This will give you an idea, how to read control record.
I do not know if option-2 of changing control record in file will affect anything else or not.
Let me know if you have any question.
Regards,
RS

Error when determining the inbound interface

Hi Experts,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Scenario Steps
1) No Condition in Interface Determination
2) 0..unbounded in Message Mapping and Operational Mapping.
3) E1KNA1 is mapped to E1KNA1
4) E1ADRMAS is mapped to E1ADRMAS
5) One Message Mapping and 1 Operational Mapping.
Thanks in Advance.
Sriram.

Hello,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
Since your scenario makes sure that the 2 files are created, there is no need to use multi-mapping. Rather, you can use an interface determination split. To do this:
1. declare xml_file1 as service interface 1, xml_file2 as service interface 2
2. do not change target occurrence in message mapping and operation mapping, maintain it as 1..1
( 2 operation mappings)
3. in ID, add the two service interfaces in your interface determination
At runtime, it will split into two inbound interfaces.
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Were you able to declare the 2 xml_files as two separate service interface(different names) in your operation mapping?
Hope this helps,
Mark

EDI Inbound Interface

Similar Messages

Maybe you are looking for