Idocs failing at seebeyond(MIDDLEWARE SYSTEM)

Hello
We have some idocs which are failing at seebeyond(middle ware system ) .The reason for failing is as follows
"Mandatory field LIFNR in segment E1EDKA1 missing when PARVW=ZM".
It is saying Mandatory field LIFNR in segment E1EDKA1 is missing when qualifier PARVW=ZM
Can any body suggest me how to proceed with this issue.

Hi,
consult your middleware expert or check the IDOC settings, filters and so on.
Cheers,
André

Similar Messages

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.

Outbound IDocs are not visuible in Middleware system(SeeBeyond)

Hi Experts,
We need need your expertise help on this issue.
Issue:
The Outbound IDocs which are in status 12 in SAP system are not visuible in Middleware system(SeeBeyond) for customized message type( forecast -ZFOSHT)
If we create a IDoc by using customized program, IDoc(eg.0000000012345678) is successfully created and the status of IDoc is 12. but not visible in Seebeyond.
but If we are re sending the same IDoc(0000000012345678) through WE19(IDoc creation) without changing any thing,the newely created IDoc reached to the Seebeyond.
Please look the issue and help me on this.
Raghavendrarao.R
+91 9739006564

Hi,
After your Function module for IDoc creation either it is Z function module or standard one "MASTER_IDOC_DISTRIBUTE" write these
CALL FUNCTION 'DB_COMMIT'.
CALL FUNCTION 'DEQUEUE_ALL'.
COMMIT WORK.
This should solve your problem.

Idoc failed in Bi system "Could not find code page for receiving system".

Dear Experts,
i am getting below error ,Idoc failed in Bi system "Could not find code page for receiving system".
All the idocs have been successfully posted except one which is giving this error
Idoc status 02 - could not find code page for receiver system.
Please guide me
thanks
vamsi

Hello Vamsi,
check Note 647495 - RFC for Unicode ./. non-Unicode Connections
If your ERP system sends e. g. chinese data to the SCM system, how should the system know which codepage to use? You have to set the MDMP flag in your ERP system in SM59 and configure in the MDMP extended settings which codepage should be used for what language.
Please check this thread - IDoc error - Could not find code page for receiving system
Hope it helps,
Thanks & Regards,
Amit Barnawal

IDOC sender: Error in Logical system name?

Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
Sowkhya

Hi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya

IDoc failed with the error massaeg "Instance of object type could not be ch

Hi All
I am getting IDoc failed with the error massaeg "Instance of object type could not be changed"
Message type :PORDCR
Basic type : PORDCR05
Message no. BAPI003
Status : 51
All POs are get uploaded in SAP during Cut over activities only.
Please suggest on this.It will be a great help.
Thanks
Ajit

Hi
After uploading POs into SAP we are changing quantity and value in PO in Legacy system, and for this all IDocs are failed, subsequently these changes are not triggering to ECC.
Please help
Thanks
Ajit

IDOC to and from eternal system

Hi All,
I've following scenario:
Sender SAP R/3 system is sendind IDOC of type say A to XI system, XI system is mapping IDOC of type A to say IDOC B, then finally XI is sending IDOC B to receiver SAP R/3 system [External system}
Note: Reverse scenario is also there in which we are receiving IDoc from external r/3 system and mapping it to different IDOC in XI then sending to SAP System.
Development done so far:
ID:
I've imported IDOC A in XI. SInce I didn't had authoriztion to import IDOC B from target so I asked client to provide XSD od IDOC B.
I created one inbound message interface using IDOC B XSD and also completed the mapping part using same XSD.
IR:
I've created one IDOC receiver communcation channel for external system. I completed the configuration
ALE:
I've created on RFC destination of type 3 to connect external SAP system. I created port in IDX1 for IDOC communcaition.
Problem:
When I am sending IDoc to exxternal sap system then message is getting failed in moni. IDoc adapter is not accepting the message interface creted based on IDoc XSD.
I believe I need to import IDoc meta data from target system for IDOC B. since in XI i didn't imported IDOC instead I used IDO XSD.
it may be the reason.
Please help me to solve the problem

HI Experts,
I am doing testing of my scenario.
As I've described the scenario in my last post. I am sending a IDoc A from my sender system and traslating it to IDoc B in XI, then sending it to the external SAP system (SAP 4.6). Basically IDOC XI IDC scenario but with the slightly change of converting one idoc to other.
During test:
I received following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Trace:
<Trace level="1" type="T">Parse XML-BODY</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPLSD</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
I've created one idoc port in XI named 'SAPLSD' inside I've used RFC destination to the target system. During runtime metadata is not loaded in IDX2.
When I tried importing metadata manually, i received the following error
"No RFC destination is maintained for the port"
is there any particular naming i should use for idx port and for rfc destination??
what could be the problem?? ....
Q. is it because of the RFC destination is not OK or
Q. the I do not have proper authoirsation to import metadata from LES system or
Q. Since target system is SAP 4.6 system.... is it could be the problem? [Unicode]
Please suggest

JDBC to Idoc scenario - change of logical system name

Hi,
I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
Did i miss something resp. how can i load the current configuration from SLD?
Thanks in advance
Michael

Hi Michael,
Again Import the changed logical system in the Integration directory of you PI system.
And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
If they are showing old system then you have to replace the business system in all the scenario.
Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

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

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

Mail to be triggered when IDOC fails

Hello experts,
I have created a responsibility and added list of user to it. I have been to WE20 and assigned responsibility to one of the logical system and message type "ORDERS". Whenever an IDOC with message type "ORDERS" fail, respective persons of responsibility shall get mail.
Please let me know what all I need to do.
Thanks,
Krishna.

Hi,
You can achive this in the following way,
1. create a custom workflow to send mail
2. go to Transaction WE42 and select your process code
3. Open the process code by double clicking
4. Here you can find the funtion module ( Identification field ) to process the inbound IDOC.
5. select the button attached with Identification
6. You can find there are several box..
    Select the 'Idoc' Box
7. Here you can find the
   Object Type
   Start Event
   End event
   Success Event
    You can can maintain the requrired event here which will trigger if any idoc failed.
    e.g.
    Object Type                         IDOCHRMD
    Start Event                         INPUTERROROCCURRED
    End event                           INPUTFINISHED
8. link this start event with your custom wokflow.
9. When ever the idoc fails event INPUTERROROCCURRED will trigger and this will start the custom workflow.
Hoping that this will help you.
Thanks and regards,
SNJY

Check Connection of Communication Arrangement for SAP ERP Financials Using IDoc Failed

Dear experts,
We are checking outbound connection from C4TE to ERP in Communication Arrangement for SAP ERP Financials Using IDoc Failed.
We get the attached error message:
Checking connection failed
Error accessing service; Service Ping ERROR: Forbidden (403)
What could be the reasons, in ERP side, through Tcode SMICM, we didn't see any log from C4TE side, and we cannot ping the ERP side successfully.
One more thing, in C4TE, we tried to set the connection to an SAP internal ERP system, and the connection was successful. But when relinked to the customer ERP system, connection failed.
Could it be firewalls reason?
Thanks!
Best regards,
Wendy

Hi Wendy,
Yes the assumption could be one reason as well for the error (403 forbidden), but there could be several other aspects also to get the 403 error, for better understanding the reason for the error, may I request you to create an incident send it to us.
Also please try once running the scenario in C4T and check if the relevant documents are being sent through Outbound Service or not.
Thanks & Regards,
Bharath

HR Time IDOC Failing

Hi All,
We are sending Time IDOC (HROT_UM) to Third party System to process Payroll.
We are using Program RPCEMDU0_CALL to generate Idocs.
and we are using standard Idoc.
When we are doing any historical data changes to infotypes the IDoc is failing because the data in Interface tables is different.
I am removing those employee who's data is changed and running the IDOC.
and for Changed employees i am running same program in Update mode.
IS there any better solution for This?
We are doing this from long time.
Pl advice?

HI Eswar,
Thanks for your ans.
When I have to run this program.
Before Genarating Idoc?

HR IDOCS failing for Info Type 1002

Guys, I am moving from business side of SRM to techno/functional. We have HR data replication IDOCS failing from R/3 to SRM with the following error. Any help on how to debug this further and your thoughts/experience on this error
Error: insertion of infotype 1002 (return code 3 )
Message no. 5-133
Diagnosis
An error occurred when you tried to insert infotype 1002 using RH_INSERT_INFTY (return Code 3).
Thanks

Hi
This is a system bug.
Please go through the following SAP OSS Notes, depending on your SAP version/Support pack ->
Note 185422 HR-CA-ALE: Error with RH_INSERT_INFTY
Note 890704 RH_INSERT_INFTY: Inserting in the structural authorization
Note 832395 HRALX: Status 51: Insertion of infotype 1001
Note 766882 HRALX: Error when inserting infotypes
Note 850259 HRALX: Position deleted or not changed
Note 445336 Different ADATANR for to and from relationships
Note 532675 Interface correction for RH_OBJID_REQUEST and RHP_CRMQ
Note 451578 Error in module BBP_UPDATE_ORG_ADDRESS
Note 440135 Short dump NO_AUTHORIZATION when creating HR work center
Hope this will help. Do let me know.
Regards
- Atul

Inbound BOMMAT idocs failing with MSG BOM 023

We're taking in BOMMAT idocs into an ECC6.0 system from an external system and I have some failed idocs with message BOM 023 - local BOM <material> <plant> <alternative> cannot be changed via ALE.
We're doing create and change functions - this one is a change with MSGFN = 005
There are no multiple BOMS, alternative 1 the only 1.
I haven't been able to find any sensible explanation for this message and I haven't seen it before . Can anyone throw any light on it?
Thanks,
Jonathan

Hi Jonathan,
You are trying to change a BOM on SAP that was not initially transfered-created via the interface. Instead it was firstly created manually on SAP. For this reason you get the message for local BOM that cannot be changed via ALE. You can also confirm this also by the ALE indicator on BOM header (field STKO-ALEKZ for the given BOM).
Br,
Petros

Idocs failing at seebeyond(MIDDLEWARE SYSTEM)

Similar Messages

Maybe you are looking for