Error in IDOC processing - Message no. VU 014

Hi All,
I got error while processing IDOC manually as:
" Incompletion: Vendor : Account number of vendor or creditor (VBPA -LIFNR ), error group: 08"
Details of Error message are as below:
Message no. VU 014
Diagnosis: The incompletion check reveals, for analysis purposes, any incomplete documents.
The message contains:
1. A description of the incomplete document
2. A technical entry, telling you which table field has been checked
3. A the error groups in the transaction from Customizing for Incompletion Log.
Procedure
One solution is to deliver the affected document in the screen (Create delivery with reference to order), and to edit and save the delivery following the menu path: Edit -> Incompletion.
In certain circumstances, you can change Customizing so that
the checked field is no longer assigned to the error group
or
assign another error group to the document type /item category
or
permit the delivery as a subsequent function.
I am confused about what could be the root cause of the error and how to solve it.
The Important thing is, when IDoc is run in Automatically(batch run), then it is successful with no any error but it gives this error when i run it manually.
Pl. guide me to solve this problem.
Thanks,
Jai.

Hi Bernd,
Thank you for your mail.
The Note 991410 is related to the IDoc status 53. I stucked with the IDoc status 51.
IDoc error message is in status 51. But still I am looking all other alternative inculding one you suggested.
Thanks you very much.
Jai.

Similar Messages

Out of memory error occurred while processing message at RFC receiver

Hi Experts
Hi Experts
i have a scenario file to RFC BPM bridge Sync/Async,
i´m getting this error when this BPM is trying to read the RFC
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: Out of memory error occurred while processing message at RFC receiver
please somebody can you help me

Hi,
No need to restart the server. In PI there is a parameter 'java Heap' indicating the size of data processed adapters. Check if it is necessary to increase the size of this parameter.
Check the note: 1173398
I hope to help you
Regards,

Error During IDoc Processing

Hi friends,
i want to transfer data in between two systems.
i have created my own message type = ZSACH
Basic type = ZSACH1
segement = ZSACH
model view = new_model
when i am execuiting this IDOC by using the program i am getting the error as
EDI: Syntax error in IDoc (segment cannot be identified)
here i am giving the coding what i have write in my program
parameters :p_logsys like tbdlst-logsys.
data : gen_segment like edidd-segnam value 'ZSACH1'.
data : control_dat like edidc,
       control_dat1 like edidd,
      gen_data like zsach .
tables : zsach1.
data: begin of inttab occurs 0,
        lname type zsach1-lname,
        fname type zsach1-fname,
      end of inttab.
data :
      int_edidd like edidd occurs 0 with header line,
      int_edidc like edidc occurs 0 with header line.
select * from zsach1 into corresponding fields of table inttab.
if sy-subrc ne 0.
message 'no data' type 'I'.
exit.
endif.
control_dat-mestyp = 'ZSACH'.
control_dat-idoctp = 'ZSACH1'.
control_dat1-segnam = 'ZSACH'.
control_dat-rcvprt = 'LS'.
control_dat-rcvprn = p_logsys.
loop at inttab.
gen_data-lname = inttab-lname.
gen_data-fname = inttab-fname.
int_edidd-segnam = gen_segment.
int_edidd-sdata = gen_data.
append int_edidd.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control                  = control_dat
*   OBJ_TYPE                             = ''
*   CHNUM                                = ''
tables
    communication_idoc_control           = int_edidc
    master_idoc_data                     = int_edidd
exceptions
   error_in_idoc_control                = 1
   error_writing_idoc_status            = 2
   error_in_idoc_data                   = 3
   sending_logical_system_unknown       = 4
   others                               = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno.
else.
loop at int_edidc.
    write :/ 'IDOC GENERATED',int_edidc-docnum.
endloop.
commit work.
endif.
<Added code tags>
can anyone give better solution for this error..
i have searched in SDN but i can't get the better document
thanks in advance.
Regards,
kk
Moderator Message: Please use "code tags" to format your code.
Edited by: Suhas Saha on Nov 9, 2011 12:59 PM

Hello kk,
It is very clear from the error message
EDI: Syntax error in IDoc (segment cannot be identified)
that there is some problem with the segment name.
When i look at your code snippet i can see there is a mismatch in the segment names passed in the IDoc control rec & the data rec.
control_dat1-segnam = 'ZSACH'.
int_edidd-segnam = gen_segment. "gen_segment like edidd-segnam value 'ZSACH1'
BR,
Suhas
PS: Before searching in SDN try to put-in some self-effort, saves time actually

JMS error - Failed to process message

Hi everybody,
I got the following JMS exception during message processing. I do not really understand what the root cause:
sendMessage(Message) - Exception sending message in thread [0] : Failed to process message: Failed to add message=ID:b8591990-c1ab-1004-8625-3433a788d95f, destination=QueueName3 (5)
javax.jms.JMSException: Failed to process message: Failed to add message=ID:b8591990-c1ab-1004-8625-3433a788d95f, destination=QueueName3 (5)
at org.exolab.jms.messagemgr.MessageMgr.add(MessageMgr.java:199)
at org.exolab.jms.server.ServerSessionImpl.send(ServerSessionImpl.java:205)
at org.exolab.jms.server.net.RemoteServerSession.send(RemoteServerSession.java:152)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:553)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:511)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
If someone has an idea, I would appreciate a lot!
Thx!

No, Iam just storing a simple message say "Hello" in the queue, the message is stored in the queue but it is shown in the below format when I opened that file in Notepad:
UUªª ªªUU ‡ÿãÂ- ‡ 6›4•Z 6›4”öÿ Â
Ô£9™ÿÿ¬h ÎM o „ fÂ6›4”ñ Trial4 com.sun.messaging.BasicQueue Hai ªªUU
and soon Iam getting this error below:
[Fatal Error] :1:1: Content is not allowed in prolog.
JMSBC-E0713: Failed to process JMS message [com.stc.jmsjca.core.WTextMessageIn@1e377d5] in onMessage: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.

BOM mapping with change number error during IDoc process

Hi all,
i am creating BOM using IDoc BOMMAT04.i have checked this IDoc will use FM IDOC_INPUT_BOMMAT inside.
in this function module, it is using FM CSAP_MAT_BOM_CREATE and CSAP_MAT_BOM_MAINTAIN to create and change.
currently, creation and deletion is success. but when change, if the change number passed as an input parameter, the IDoc process error saying that the BOM header not allowed to update for read-only field.
if i not pass the change number, the change will be success, but no change number displayed in the item. that is not the user expected.
and if i delete the bom with change number, create a new BOM for the same material is not aloowed, saying that BOM already existing.
it seems that CSAP_MAT_BOM_CREATE and CSAP_MAT_BOM_MAINTAIN cannot support much. it is limited.
can anyone have any good solutions? thanks!

yeah, for the change, i have solved it.
but currently, if i delete the existing BOM with a change number, the re-creation is not allowed by the IDoc saying that the BOM already existing.
if i delete in CS02 without change number, it deleted from DB and can be re-create.
but if delete in IDoc without change number, it failed saying that local BOM can not be deleted by ALE.
do you have any solution? i want to implment in IDoc: delete existing BOM and create a new one for the same material with change number. (currently the standard IDoc FM not support BOM group)

Error RFC Idoc Inbound: Message E0(285)

This is a message into trx SM21:
While reading the first record to process the input file IDoc & & v1, there was an error.
Check the file & & v1.
Also check the meter protocol that allows the state of processing the file in question. The error may in fact be
due to an inconsistency of the counter.
What is the problem?
What is the inconsistency of the counter ?
Thanks.
Unga00

Hi,
I think you are trying to make it as an R/3 system connection. The 3rd party programs should be connected as TCP/IP connection. This function module will be looked upon in SAP systems for ALE. Please check.
Cheers
Suresh

Error in idoc process

I am new to EDI / IDOC. Manual bill is not being created.
In TCODE EA18 I am facing an error that the EDI 810 failed to process , idoc - Application document not posted - Datex Process Error.
Can anyone suggest me what to do for resolving this error.
Thanks in Advance.

Hi,
change names while creatingwork are for that.
maintain order of the segments in order as for idoc.
check whether you are maintaining orderly or not.

Error in IDOC Processing

hi all ,
I am getting error No. 26 while processng IDOC. error is Segment Cannot be identified,
Mandatory segment missing. how can i resolve that error
actually i want to add one zsegmant to standard basic type DESADV01.
please give me a detail stepwise procedure for adding that segment with transaction
is there any type of setting that i have to maintiain after adding that segment.
please give a solution.
thanks,
vinod

go to BD56 tcode ..give the segment and check is it available with DESADV01.If no....go to WE30 create zidoc with your own segment...now extend your DESADV01 idoc type by selecting the radio button extension idoc type and add here your own zidoc...in the first screen you select as this segment as mandatory.
<REMOVED BY MODERATOR>
Dara.
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 3:51 PM

Syntax error in IDOC process

Hi,
We are getting syntax error in ORDERS01 IDOC. I have checked the E1EDP19 segment's maximum occurence is 5 which is a child segment of E1EDP01.
But the my outbound IDOC had more than 5 occurences in the segment E1EDP19.
It look to me that because of this we are getting syntax error. Please correct me If I'm wrong.
How can I change the maximum occurence value in an standared segment.
Thanks,
Dharmendra

Hi,
change names while creatingwork are for that.
maintain order of the segments in order as for idoc.
check whether you are maintaining orderly or not.

Error during proxy processing Message E SG 105 cannot be processed in plugi

When I move a new custom proxy from Dev to Qa I am getting the above error when running the test from XI. However, the test runs fine in SPROXY test tool. Has anyone else run into this problem in the past? The error catagory is Dynamic_Call_Failure
Thanks,
Chris

Hi,
I'm facing the same problem.
I wrote an very easy report. It works as intended, but when i set fillable='X' i get the error FPRUNX 001.
FP_GET_LAST_ADS_TRACE return following:
Begin operation:
Render, elapsed time = 16 ms.
#   End operation: Render, elapsed time = 89 ms.
#   Begin operation: UsageRights, elapsed time = 89 ms.
#   End operation: UsageRights, elapsed time = 97 ms.#
...and the error string of FP_GET_LAST_ADS_ERRSTR is:
ADS: Request start time: Wed Jul 01 14:44:26 CEST 2009(200.101).
Any idea what the problem might be?

Error in IDOC generation

Hi Gurus,
I have got an Error in IDOC Processing from other interface.
The IDOC status is 51 and we are using it to create Promotion Deal in
SAP ERP through IDOC from other interface.
The Error i am getting in Status Record is that "Promotion is Duplicated
along with Promotion Deal Number"
I have also checked the Promotion Deal No in VB 33 but it is not existing.
Please could you suggest where is the possible error.
I have also checked the Control Record it is correct.
Awaiting for response.
Thanks,
Sam.
+

Hi,
Reprocess the IDOC by using the T.Code "BD87".
Even if the same error persists,try to change the data manually by using the T.Code "WE19".
Check with the ABAPer for debugging the code.
Regards,
Krishna.

Error during proxy processing

Hi Experts,
We have a web service hosted on PI and getting the Tax Jurisdiction values from Taxware via ECC(ECC has a TCP/IP connection to connect to Taxware system, From there ECC gets Taxjurisdiction Codes and gives back to PI).
When we make a call to this Web service following Error response has been given. Please let us know what could be the reason.
<?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="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1 />
<SAP:P2>ZCL_GET_TAX_IN</SAP:P2>
<SAP:P3>GET_TAX_JURISDICTION_SYNC</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing Message E TAX_TXJCD 110 cannot be processed in plugin mode HTTP</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Thanks,
Sekhar.J

Hi,
We are using XI adapter. The same Web Service is working good in Development and Quality Enviroments, I am wondering why it is failing in Production Environement intermittently. And also in ECC we are using TCP/IP connection to fetch Tax Jurisdiction codes from TaxWare System. This TCP/IP connection was configured in SM59 of ECC. PI will make call to ECC and ECC will make call to TaxWare and returns the result back PI.
Thanks,
Sekhar.J

Inbound IDoc w/message ORDERS - issues with error processing

We are using inbound IDoc ORDERS05 with message type ORDERS to create the sales orders in SAP. In WE20 we have the following settings:
- partner type LS (= Sales Org VKORG)
- process code ORDE
- trigger by background program
- post-processing agent of type US (user) with a user ID.
We create IDocs through an ABAP program and use RBDAPP01 to post the IDocs. When there is an application error in the IDoc posting we expect the designated user to receive a workflow item in the SAP Inbox, but for some reason this is not happening.
I did some research and went through all the possible settings for workflow, task, etc. and everything seems to be set up correctly. When debugging RBDAPP01 I have noticed that it calls FM APPLICATION_IDOC_POST_IMMEDIAT, which, in turn, calls IDOC_START_INBOUND. If IDOC_START_INBOUND returns SY-SUBRC = 1 then the workflow item is sent correctly to the designated user, exactly as we want. But for some reason it returns 0 (I changed it to 1 in the debugger).
It seems that IDOC_START_INBOUND reads TEDE2 records (TEVE2-EVCODE = ORDE) and sy-subrc = 1 is only possible when EDIVR2 is 1,2,3 or 4. In our case TEDE2-EDIVR2 = 6. It seems that TEDE2 is maintained in the transaction WE42. However, I tried to change the settings there but it affects the IDoc processing in whole (IDoc gets some odd status and doesn't get processed as before). I've also tried to use process code ORDE_BY_WORKFLOW in WE20 with the same "success".
What do we need to do to get a workflow item for the errors that happen in the application layer when IDoc is posted? Is it even possible with this message type?
Any ideas would be appreciated.

Hi,
Can you please share how do you overcome the problem, so that it can be helpful for others.

Error on outbound processing (- to IDoc), nodetailed error message

Hi guys!
I'm facing a problem with sending IDocs to R/3. My messages have red flag in outbound status, but there is no detailed error message. Everything seems to be ok, but my IDoc doesn't arrive to R/3 and there is that red flag in XI.
What could cause this? It seems like there is some communication problem. Any ideas?
Thank you,
Olian

Hi,
IT will give the status number,what is the status number in IDOC check it and update the thread.
if u find its a data problem u can debugg the FM,go to WE19 and give ur IDOC number and there u will find the option start out bound processing form this opion u can debugg the code and know wat is the error.
Check ur ALE settings.
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Regards,
Phani
Reward points if Helpful

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Error in IDOC processing - Message no. VU 014

Similar Messages

Maybe you are looking for