IDOC error using PREQCR102

Dear All,
I am looking for some help in the below issue.
We have an inbound IDOC scenario, we are using PREQCR102 IDOC type to process incoming PRs.
I still receive errors during the IDOC test in WE19.
The error refers to "Enter Plant" and "Enter Quantity" although these fields have a value in the segments.
I received hints that I incorrectly use segment E1BPMEREQITEM and should use E1BPMEREQITEMIMP. However when populating E1BPMEREQITEMIMP I got the same errors and in addition I receive an error(Maintain services or limits for Item 00020) related to item 20 which is not in my IDOC at all.
I attached my IDOC contents hope this helps.
Thanks in advance for any help.

For the notes, the solution was to add requisition item number to some additional segments(like delivery address and some other) as technically this is required in SAP.

Similar Messages

File-to-Idoc error (using business sender service)

Hello,
My scenario is Flat file to IDoc. I am using a business service as my sender system. I did put in a logical system name in the business service and I have added the logical system in SALE.
The error I am getting is <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 526719BA7E874E3906EEF45B43806D5C: Tag CULL_GR_RECORD found instead of tag IDOC BEGIN=</SAP:P1>
This is confusing to me because the CULL_GR_RECORD is the name of my data record of the file that is converted into an idoc within XI.
Can someone please help me with this? I would really appreciate it. I need to solve this tonight.
Thank you.

Hi,
>> I am using a business service as my sender system.
This is fine as ur sender is file.
I suggest deleting the matadata in IDX2 and then rerun the entire interface.
Make sure ur IDoc is imported properly to the IR. If yes, test ur mapping locally once.
Regards,
Divija.

Receiver IDOC error - using TCP/IP

Hi All,
I have a scnario where I am sending an IDOC to BCOMM ERP system via IDOC adapter from SAP PI using TCP/IP RFC program but while sending it is giving me an error in SM58 as IDocException occurred and there isn't much info in SM21 or ST22 or any other transaction.
Error log in SM21 says
Name of the partner program where an error has occurred. Check the
preceding system log entries.
Use the gateway monitor (transaction SMGW) to monitor the functions
of the gateway.
If someone has ever worked on such a scneario please let me knw and any pointers would be great.
Cheers
Abhi

Hi Michael,
I know that this is not the conventional way but we cannot use RFC of type 3 as it is not a ECC system , it can handle IDOC communication via Idoc adapter through a SAP connector at there end which can be handled only via TCP/IP.
I am able to do it for another system with similar scenario but Not able to do for this particular system.
Can you tell me about your scenario and how you did it?
Thanks for your reply.
Cheers
Abhi

IDoc error In case of ERS procedure, please enter terms of payment

Hi,
I tried to use BAPI_PO_CREATE1 to post purchase order. However, I encountered this error.
IDoc error In case of ERS procedure, please enter terms of payment
I passed the payment term in IDOC PORDCH. Segment E1BPMEPOHEADER-PMTTRMS has value filled out. This value is passed into the BAPI correctly but for some reasons, it got cleared out in the BAPI. Any ideas or suggestions would be greatly appreciated.
Thanks

Check
BAPI_PO_CREATE1 - E 06 436 In case of account assignment

IDoc Errors in ECC

Hi Experts,
what kind of IDoc Errors can occur in ECC for the scenario :
ECC sending PO to Ariba(E-commerce hub, using third party adapter) and in receiving back Order confirmation from it.
Thank you,
MK

Hi,
This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
some hints:
1. Connection Problem: Because of timeout , unavailability of the Receiver system.
2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
3. User ID and Password Maintenance - it may hit sometimes
4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
these all kind of problems you may face..
Rgds , Moorthy

IDoc Error 51 - Make Entry in All Required Fields

hi,
I am using a scenario where an idoc is being posted into an R/3 system from a legacy application. For some reason I keep getting Idoc error 51 (Document not posted).
Once I drill down further, the specific error states "Make entry in all required fields". Have checked to make sure all mandatory fields have been mapped and proper constant values have been specified.
But cannot seem to get rid of the problem. Could anybody help out in determining how else to troubleshoot this and identify the possible cause?
thx,
Manpreet

Manpreet,
What IDoc Type you are trying to post ? One way is debugging the inbound function module using WE19. The second option is talking to a functional consultantor who worked, what fields are needed for that particular IDoc.
I wouldn't care much about whether the IDoc is posted or not because, it is the ABAP ALE/EDI consultant's job to do that. The only way XI Developer is concerned is when it is not posting, ABAPer would tell what's missing.
Hope this info helps.
regards
SKM

File to IDOC - Error Inbound -56

Hi,
I am doing file to Idoc. (CREMAS01).. My scenario in
RWB is successful. But in R/3 it is shwoing IDOC
error :"EDI: Partner profile inbound not available".
I created Partner Profile in R/3(logical name of BS-
sender file). Still is shwoing Error.
Regards,
Mukharji
Message was edited by: Mukharji T

Hi Mukharji,
I hereunder give you the step by step procedure for File to IDOC scenario. Cross check whether you have done all these:-
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 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 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
Hope this helps you.
Regards.
Praveen

File to Multiple Idocs, Error: Tag MESSAGE1 found instead of tag IDOC BEGIN

Hi,
I have configured my file to multiple idocs scenario using the following blog -
/people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool
Now when i try to execute this scenario it is scenario it is giving me the following error at "Call Adapter" Stage in runtime-
"Tag MESSAGE1 found instead of tag IDOC BEGIN="
My message looks like this at "Request Message Mapping" Stage in runtime -
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
- <ns0:Message1>
- <ZDR009>
- <IDOC BEGIN="1">
- <Z100901 SEGMENT="1">
<RUNDATE>20080220</RUNDATE>
<RUNTIME>0037</RUNTIME>
<CONSTANT1>PYRLINCST</CONSTANT1>
<CONSTANT2>CSC</CONSTANT2>
- <Z100902 SEGMENT="1">
<RECTYP>2</RECTYP>
<SSN>641381239</SSN>
Kindly assist me in solving this error, Thanks in Advance!!
Regards.
Sudheer

Hi Sudheer,
Just the check the message mapping. Check the parant node mappings to create two different messages.
It seems that the mapping done on IDOC Node to create the IDOCs is getting failed.
Copy the content from inbound payload and test it in message mapping.
Remember, when you load the test data into your test tab you will get the error of structure mismatch coz in your mapping you have additional message.
Do the change with original data as shown below befor testing.
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
Original message will be here.
</ns0:Message1>
</ns0:Messages>
Regards,
Sarvesh

File to IDOC Scenario using BPM

Hi Experts,
    I am working on file-Bapi-Idoc scenario using BPM.
    I have two conditions
1. If the Sonumber is populated then need trigger an Bapi_change
2.If the Sonumber is not populated from the file then need to trigger a Bapi_Createfromdat to create the sales order and receive the salesorder number as response from Bapi
and the response of these BAPIs should be validated whether the Bapi is successful or not.
If it is successful message then need to trigger IDOC or else should throw an alert message.
let me know the steps involved in this scenario.
can i send alert message to other email IDs or can i send it to only XI admin?
Please let me know u r inputs.
Thanks in advance
Praveen

Hey,
You need to have a BPM for this.
BPM design.
Recieve step(abstract asynchronous) for file structure
Switch Case(condition whether sonumber is populated or not)
if populated
Branch 1(of switch)
    transforamtion step:- mapping between File and Bapi_Change(Request structure)
Send step(abstract syncronous) To send the BAPI_change
Branch 2(of switch)
transformation step:-mapping between file and BApi_Create
Send step(abstract synchronous) To send the BAPI_Create
Block step(which will include the Switch step)
    trigger an Execption in case of an error(in any of the two branches) through the block
    The Exception will trigger an alert.
Now after the Block step there will be a transformation step(which will have the mapping between RFC response and Idoc)
Next is the send step(abstract asynchronous) for the idoc
In case if there is no exception the Idoc will be triggered or the exception branch will trigger the alert
rewards points if useful
regards,
      Milan

Idoc monitoring using WE06

Hi all,
I want to do Idoc monitoring using the tool Active Idoc Monitoring(Programm: RSEIDOCA;Transaction : WE06).
So when ever something goes wrong in an Idoc,depending on the idoc type ,I want to inform the concerned person by email using SAP mail( Business Workplace).
My questions are with regard to the 2 possibilities(I thought) stated below for achieving this.
[1]
Is it possible to directly send an email to the SAP mail inbox of the concerned person,using this program depending on the Idoc type and other conditions if they exists .Because depending on the idoc type different users need to be informed of the error.
I made a variant as said below in the link.
http://help.sap.com/saphelp_470/helpdata/En/dc/6b81b943d711d1893e0000e8323c4f/frameset.htm
Is it possible to test this case immediately by sending a error ORDERS Idoc.If yes,How?
Is the configuration said in the above link sufficient or Is there any need to make any further changes.
OR
[2]
Using transaction WE06,I want to the send the email to my sap mailBox and from there forward it to other users depending on the conditions said above.
How could I achieve it? Test it immediately
I would like to go forward with this 2nd solution,if thats better and easily configurable.
How to configure this scenario.
Any help is greatly appreciated.
Regards
K

Closing this thread.Moving it to a more appropriate forum.

IDOC error while receiving

Hi Friends,
In my scenario, I have to receive P.O. message from partner in to my R/3 system.
I am using PI 7.1
When partner is sending me message I am getting error , "Only asynchronous processing supported for IDoc adapter outbound processg" in SXMB_MONI
I tried to find solution on sdn, and I got 2 related foroum,
Idoc Error
Re: No receiver could be determined. (File to Idoc)
But from this also I am not sure hw can i solve this error.
Please Suggest.
Thanks & Regards,
Brijesh Soni

Hi
For Error Only asynchronous processing supported for IDoc adapter outbound
IDOC adapter support asynchronous only,
Check Quality of Service in your sender adapter. Should be EO or EOIO, not BE.
This thread had same problem and resolved :
Re: No receiver could be determined. (File to Idoc)
In Your case QOS is BE. Plz check in your CC if and BE is by default..
If you use BE, HTTP expects a Response back and as IDOC does not support BE, you go the earlier error.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 21, 2009 3:14 PM

Thousands of IDOC Errors

Hi there,
I have recently configured workflow using SWU3 - Now suddenly there are about 10 000 new work items in everyones inbox - All related to IDOC errors.
I have made sure that the workflow administrator is set to a specific user, and in WE46, the IDOC administrator is also set.
Most of the wor-items are back-dated to about a year ago, way before the workflow was configured.
Firstly, why are all these appearing now?
Secondly, how can I get rid of them, or at least isolate them into only one persons inbox?
This is on our test system, so there is no need to investigate any idoc errors...

This is happening because you have made some program run in background while configuring SWU3 most probably the deadline program.
You can get rid of them by checking the Workflow Log and then investigating from where agents are getting determined and accordingly changing the agents to a particular user Id.
Reward points if useful

IDOC Error V1 042 - Sales document X is currently being processed by user X

Hello Experts,
I am using the IS-Retail solution of SAP and I am facing a IDOC Error which keeps the IDOC in Status 51. I traced the Error Message and it was V1 042. I am using an Inbound IDOC 'SHP_OBDLV_CREATE_STO01' to create the STOs (Deliveries) using the POs and there is a locking issue of the PO giving error message 'Sales document XXX is currently being processed by user XXX'.
I have created a backgroung job using a program to post the STOs using IDOCs that picks up multiple files from Application Server and processes them one by one. Now when 2 or more files use the same PO then this error occus.
I added a couple of minutes of wait time between the file processing but that did not help.
Please let me know if you have faces same situation and what solution did you apply.
Regards,
PS

Hopefully you have fixed this by now, but for anyone else who might be looking at this problem. We had this problem and we had the 2 programs check to see if the other was already runing. If so the program would submit itself for a number of minutes, different for both programs, and then exit. We also, and just before this, checked to make sure that there were not 2 of the running programs running and if so to exit. This was necessary because re-scheduling could put a program in conflict with itself. I hope that this may help someone. We used the join V_OP and searched for the program name, not the job name.
Kevin

Missing IDoc and recurring IDoc errors

Hi,
I would like to ask for a help or any ideas on below case.
We encountered almost everyday a number of generated IDoc errors and the number increases everyday. All of these IDocs has Status "51" (application document not posted) and description "EDI: IDoc 63120 does not exist, please check data".
This IDoc errors does not happen before. It only started when the IDoc 63120 was missing and we can't find it already. We don't know why this is missing and we really need to get rid of these recurring IDoc errors whcih increases almost everyday.
Your response will be helpful in solving my problem.
Thanks in advance!

Hi Juan Francisco Zurita Duque
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
Use
Sold-to party number sent in by the customer in delivery schedules.
Use
The system uses this number to automatically determine the ship-to party.
Every thing good for ORDRE05 IN ECC6.0
Check your config settign related to Message type and idoc type.....once again.....
RR

Workflow for Idoc errors

Hi,
I am new to workflow, I got a requirement for idoc error handling in workflow.
If the idocs fail a notification needs to be sent to an appropriate personnel. If it fails due to configuration or technical issue then the notification needs to go to the tech personnel ( A distribution list ) . If it is a data error then notification needs to go to functional personnel ( distribution list ).
Here i have created a WF using Object IDOCAPPL. Please let me know how i can handle this condition and want some document on orginization structure.
I have refered to documents in Saptechinical and Sdn.Plz let me have some other ideas and documents.
thanks
Arun.

You can create a custom rule and inside that you can have your own condition and populate the users accordingly.
Distribution list..you can create in SBWP itself.

IDOC error using PREQCR102

Similar Messages

Maybe you are looking for