Inbound idoc failing to reach SAP system.

Hi All,
We are upgrading our SAP system from release 700 to 730. Post upgrade we have identified that idocs which are supposed to reach SAP as inbound are failing in Biz Talk with below message.
Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDT37003GRP IDOCTYP: SHPMNT03 Release: 700 CIMTYP: . Ensure that your message xml validates against the operation schema.
This happening for only one inbound idoc which is using SHPMNT03 idoc.Whereas other inbound idoc which is using /AFS/ORDERS05 idoc is reaching SAP without any issues. I am bit confused why this is happening for idoc SHPMNT03.
Please let me know your thoughts.
Thanks,
Gowrinath.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Similar Messages

How we can import an IDOC structure from one SAP system to another w/o ALE

Hi Gurus,
How we can import an IDOC structure from one SAP system to another? we're not able to use ALE tech, these two sap systems are isolated.
Any response will be awarded!
Thanks a lot.
Samson

hi,
1.One is by change pointer concept i.e by executing the RBDMIDOC.We can generate the idoc and automatically to the inbound System.
2.By executable program also like bd10 and bd11.
Regards,
SHIVA(reward if helpful).

Mails whenevr an inbound idoc fails

Hi Experts,
Is there any way I can trigger mails whenevr an inbound idoc fails to update in r3.With reference to workflow etc
Regards,
Arnab

Hello Arnab
On SAP release >= 6.20 you have the standard report RSEIDOCA available which can be scheduled in background.
Unfortunately SAP did not provide an e-mail notification mechanism for this report but only workflow. For our company I created a ZRSEIDOCA report having this e-mail function. For more details please refer to
ALE Error Message Handling
e-mailing: How to sent out an email to the Managers OUTLOOK express account
Regards
Uwe

Triggering a mail when ever a perticular inbound IDOC fails

Hi Experts,
Is there any way I can trigger mails whenevr an inbound idoc fails to update in r3.With reference to workflow etc
Regards,
Arnab

hi,
i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
regards,
pankaj singh

IDoc adapter with Non SAP systems

SAP XI 3.0 help says:
You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures
What does this mean?
-Naveen.

Hi Naveen,
Let me give a use-case in one of our projects ....we have 2 middlewares in our landscape...webmethods and XI...and in one particular instance there was a need to send an FI IDoc from webmethods to XI and forward it to R/3....
In this case, the webmethods was treated like any other sap system for receiving IDoc into XI(with settings in IDX1)...
Hope this might clarify a little bit...
Thanks,
Renjith

How we can import an IDOC structure from one SAP system to another

Hi Gurus,
How we can import an IDOC structure from one SAP system to another? If we're using ALE, how can we do that? Please can someone give me the process and necessary t codes.
Any response will be awarded!
Thanks a lot.
Samson

hi!
Define the logical system names in both the systems.
Logical system names :SAP001
SAP002
SAP001 FOR 001 CLIENT
SAP002 FOR 002 CLIENT
These two logical system definitions should be present in both the systems.
Assign the logical systems to the client. (in both the systems)
Assign SAP001 to 001 CLIENT
Assign SAP002 to 002 CLIENT
you can See these in transaction SALE.
After this define the rfc DESTINATION IN sm59. (in both the systems)
In 001 client create the RFC destination name SAP002
In the tab log on security, give the user name and password and client of the 002 client and save it.
Similarly do the reverse in the 002 Client.
In 001 client create the port.(Transaction WE21)
Specify the RFC destination name as SAP002.
Now you can define the ports, (both the systems)
Create the partner profile for partner(ie gve logical system name of partner) , so give as SAP002.
partner profile in both the systems.
Now create the distribution model in BD64 and goto edit>model view>distribute.
The same model view will be visible n distributed to the partner system also..which in this case is sap002.
U may trigger the idoc from we19 and chk its status in we05.
Please let me know if you need further info on this.

How to send IDocs from a non-SAP system to a SAP system

Hi everyone i am new to SAP R/3 System.
Currently i am required to send IDocs from a non-SAP system to a SAP R/3 System.
There is a guide on Cost-Effective and Quick Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface. But its from a SAP system to a non-SAP system and i am able to do that.
Is there any step by step guide where they teaches you how to send IDocs from a non-SAP system to SAP system via similar method?
Thank You!

Hi,
I hope this link may help you......
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.ds.entpak.sapr3.use.doc/topics/c_pack_r3_Introduction.html

SWCV still contains IDocs/RFCs from an SAP system

Hi
I have imported Idoc to a SWCV. Now am trying to create one more namespace under it. When I try to create another namespace, it automatically selects the check button Import of Idoc and RFC interfaces from SAP systems permitted. If I select not permitted and try to create namespace it gives me this message
Unable to save object XYZ , 1.0 of ABC
Indicator cannot be undone since the software component version still contains IDocs/RFCs from an SAP system
Delete the objects first.
Is it possible for me to create another namespace under a SWCV, to which I have already imported Idoc, by selecting the option " Not permitted ". I want to create another namespace and I don't want to select that option as I have already imported Idoc

Hi,
You no need to touch that check box, you can still create the namespace under software component.
Just double click lick on software component, goto edit mode and click on + symbol to insert namespace and save then activate.
Note:- As you have already imported the RFC and IDoc under your software component(not namspace as you mentioned), you keep that check box import of RFC and IDocs permitted. Dont try to uncheck that.
thanks,
madhu

Idoc inbound processing? from non-sap system?

Hi experts,
I'm confused with some functions below:
IDOC_INBOUND_SYNCHRONOUS
INBOUND_IDOC_PROCESS
IDOC_INBOUND_SINGLE
IDOC_INBOUND_ASYNCHRONOUS
can you tell me what are the differences? when to use them?
for sap outbound processing, we can only call function master_idoc_distribute to generate idoc or use message control to trigger outbound idoc. no other options, correct?
for sap inbound processing, if we use message control for automatical posting, we have process code which read the inbound idoc file and do the sap posting. when to use those functions above?
does the middlewares like seeburger, GIS call those functions to generate idocs at SAP side?
in what scenarios can we use those functions? read directly non-sap file into sap internal table then call the functions to create inbound idoc? how about the posting? call inbound processe code function after the functions above?
in case the interface between sap and legacy system is using above functions to build inbound idoc in sap and sap use process code for inbound posing, sap can monitor all inbound process using idoc, but how can the legacy system mornitor the interface?
Thanks.
Legend.
Edited by: legend li on Dec 21, 2010 4:58 PM
Edited by: legend li on Dec 21, 2010 5:40 PM

Hi Christophe,
Awesome!!!!!! it worked, You are the best.
I could able to create a sales order in CRM,but below are the valid data I passed in the respective segment fields.Except for first 3 values rest all did not get reflected in teh Sales order.I feel i am missing some qualifiers.
Can you kindly share the IDoc data to be passed in...along with respective segments and fields:
Segment                                                 Field
E101CRMXIF_BUSTRANS     OBJECT_TASK
E101CRMXIF_BUSTRANS     PROCESS_TYPE
E101CRMXIF_BUSTRANS     POSTING_DATE
E101CRMXIF_PARTNER                          PARTNER_NO
E101CRMXIF_PARTNER                RELATION_PARTNER_NO
E101CRMXIF_ORGMAN         SALES_ORG
E101CRMXIF_ORGMAN          DIS_CHANNEL
E101CRMXIF_ORGMAN         DIVISION
E101CRMXIF_SALES             PO_NUMBER_SOLD
E101CRMXIF_SALES            YOUR_REF_SOLD
E101CRMXIF_SALES            PO_NUMBER_SHIP
E101CRMXIF_BUSTRANS_ITEM     ITEM_NUMBER
E101CRMXIF_BUSTRANS_ITEM     ITEM_TYPE
E101CRMXIF_BUSTRANS_ITEM     ORDERED_PRODUCT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT_ISO
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT_ISO
E101CRMXIF_SCHEDLIN_I     ORDER_QTY
Thanks a ton in advance .
Vijay

Inbound IDOC Failing

HI All,
We are upgrading our 4.6C system to ECC6.We have EDI interface.We are sending and receiving IDOCs through Webmethods.
We are testing inbound IDOCs.IDOC (ORDERS03) got generated in webmethods properly, but it got reached ECC6 system with error message 51.
IDOC in ECC6 system didn't created properly.All data segments didn't filled with data.
Can you please tell me, why it got happened?Do we need to change any setting in terms of port defenitions, RFC destinations?
Kindly let me know.It is urgent.
Regards,
Srinivas.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Idoc not posted in sap system

Hi All,
i have configured the file to idoc and idoc to idoc scenario.
in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the port that is idoc comming from sap system.
in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space of the idoc ,which is not to our operational mapping created in IR.
Regards,
reddy

in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the
port that is idoc comming from sap system.
In Message Mapping enable the EDI_DC40 segment and then give value to the SNDPOR/ RCVPOR ....once done in receiver IDOC channel check the Apply Control Record from Payload....Michal has written a blog on EDI_DC40 segment check it once.
in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space
of the idoc ,which is not to our operational mapping created in IR.
This behavior is correct....IDOC will refer to its own namespace and not to the one created in IR.....and this should not cause any issue while assigning mapping in Interface Determination....if it is causing an error then you have not selected the objects properly.
Regards,
Abhishek.

Inbound MATMAS: layout from Non-SAP system

Hi
I would like to know how the layout of the inbound MATMAS file(xlm/flatfile) should look like and how will i be able to trigger an inbound update of MATMAS from an external non-SAP system without a middleware system?
Giovanni
Message was edited by: Giovanni Baumann

Hi,
It will probably be looking like a IDOC in XML format. You can go to WE60 transaction and look at the XML schema (documentation --> XML Schema), that is how your file with data should look like.
Then your program can pick up the file and pass the data to EDI_DATA_INCOMING function.
Regards,
Ravi
Note : Please mark the helpful answers

Post IDOC internally in same SAP system

Hi All,
I used IDOC to send data from SAP to XI in my previous assignments.
Now i have a requirement wherein i need to use an idoc to post data within SAP i.e in the same system. This is because incase the idoc fails the end user can correct the data and re-process the idoc and post it again. though its not so recommended its agreeded upon in the design phase.
now my doubt is in MASTER_IDOC_DISTRIBUTE should i set the control record so that it points to the same system which means the port i create which has an RFC which will point to the same system from where the report is run. is this the correct way.
thank you.
Regards,
Jayaram

Hi,
You can test in the same system
But make sure that the using partner profile(WE21) is having Collect IDOC's option so that the IDOC are not transferred to the target system.
Hope this helps
Regards
Shiva

Data elements for IDoc Segments to non-SAP system

Hi,
I need to create IDocs for transferring data to non-SAP system. When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system? Because there are many fields where the field attributes of SAP system do not match the corresponding fields of receiving non-SAP system.
Thanks in advance!!
Regards,
Sriram

Hi Sriram,
When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system
Is it custom segments .
Regards,
Madhu.

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

Inbound idoc failing to reach SAP system.

Similar Messages

Maybe you are looking for