Error posting Idocs

Hello,
I am working on sending idocs from XI to SAP R/3. While posting idocs from XI to R/3 i am getting errors on outbound side in SM58 and IDX5.
In XI it says -
Function Module:
IDOC_INBOUND_ASYNCHRONOUS
Error Text:
No authorization to send IDOCS of message type HRMD_A
I checked authorizations and granted SAP_ALL and SAP_NEW to the extraction user but still same problem.
Best Regards,
Sudheer

Hi Sudheer
First Check This
Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
Incase All this are proper
delete metatdata in IDX2 And reimport the same.
Also Check This
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Abhishek Mahajan

Similar Messages

Error Posting IDOC: need help in understanding the following error

Hi ALL
Can you please, help me understand the following error encountered while the message was trying to post a IDOC.
where SAP_050 is the RFC destination created to post IDOCs
<?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_RUNTIME</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help is greatly appreciated.............Thank you!

Hi Patrick,
Check the authorizations assigned to the user which you used in the RFC destinations, If there is no enough authorizations then it is not possible to post the idocs.
Also Refer this Note 747322
Regards,
Prakash

Error when posting IDoc *** in system ERP100

Hi Experts!
Can you pls help me with a goods receipt issue?
When user tries to make a good receipt on a PO, we have the msg "Error when posting IDoc *** in system ERP100" in SRM front-end application monitor.
The same msg is getting displayed in RZ20.
On the idoc itself in tcode WE02 however, I can't see any problem and unfortunately I have no access to the same t-code in R/3. Anyway, I don't see the GR on the PO.
What can be the reason for this problem please?
What is in general the way to analyse and solve this kind of issue?
Thanks a lot !!
imre

Hi,
First find out the PO number from the idoc in tx WE02 in SRM system. Then in ERP , transaction BD87 , specify the details like message type and the system information .... and find out the PO that was errored out for GR. From this we can find the cause of the error. First try to rectify the error and then run the report to clear the contents of BBP_DOCUMENT_TAB.
Hope this helps.
Regards,
Kalyan

Authorization error in posting IDoc

Hi,
I have completed configuration of File to IDoc scenario. When File adapter has picked up the file from FTP server, the message is processed with outbound error.
To find out the error occured at the outbound side, I ran the transaction 'SM58' which explained that XIAFUSER does not have authorizations to post the IDoc to destination system. Can somebody provide what authorizations should be given to this user to facilitate the processing of message.
In another instance the same error has resulted but notifying the different user. This time WF-BATCH does not have authorizations to post the IDoc to destination system.
As per my understanding there should be some system configuration where you have an option of specifying the user for posting IDocs to destination system.
Please confirm whether my understanding is correct and also let me know the where it is done?
Regards,
Suraj

Hi Suraj,
The user id which you are using in your RFC destination will be of your target system to login. This user id should be having all SAP_ALL authorizations attached into their profile.
Pls do try with the help of your basis by assigning this profile to your WF-BATCH user.
Cheers
JK

IDOC Tables with Errors Post System Refresh

Hi Everyone,
Is there any Report or other way through which one can get List of IDOC Tables with Errors Post System Refresh.
Thanks,
Regards,
- Ishan

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

Error in posting IDOC ORDERS.ORDERS05

hi,
dear all,
i am getting error in posting IDOC ORDERS05.
IDOC has arrived on system but with status 51,
it says:
VKORG, VTWEG, SPART cannot be determined for customer , vendor
can you please tell me how to map above specified fields.They are under which segment.
I am sending XML file with fields thru XI.
Thanks.

hey rajeev,
thanks very much for your patience to deal with this basic questions expected from me who is just new to XI
really thanks.
but RAJEEV, as you said we have to add the same IDOC to inbound to R3 if R3 is receiving that IDOC and in OUTBOUND if R3 is sending right?
hi, sorry to interrupt you more :
take my scenario of IDOC ->XI->FILE.
i added that IDOC type in receiving LS that is FILE LS in OUTBOUND side,
and i do not add anything in OUTBOUND parameters of my sending LS that is R3 system.
i am using we19 to send IDOC.
Before Sending IDOC i am filling EDIDC segment with these parameters is it right?
Sender Information:
Partner number: SAPLS
Port: Port defined on XI pointing to R3.
Partner type :LS
Receiver Information:
Partner Number : FILELS
Port: Port defined on R3 pointing to XI.
SO, Provided that i entered following values in EDIDC segment and i do not add anything IDOC type in outbound parameters in R3(sending system),
i add that IDOc in outbound parameters under LS defined for File system,it worked.
You got my point?
sorry for writing such a long thread? but please resolve it RAJEEV.
Thanks.

Error in IDoc AAE (Receiver) PI 7.3

Dear Experts,
I have a SOAP - IDoc scenario where I am using IDoc AAE reciver adapter for posting IDoc to SAP ECC system.
Message is successful in SXMB_MONI,however getting an error as below in receiver IDoc adapter.
Message processing failed. Cause: com.sap.aii.af.idoc.exception.IDOCAdapterException: com.sap.sql.log.OpenSQLException: Failed to set the parameter 9 of the statement >>INSERT INTO XI_IDOC_OUT_MSG ( IDOC_NUMBER , XI_MSG_NO , REF_NUMBER , ORIGINAL_IDOC_NO , IN_TIME , MESSAGING_TYPE , IDOC_TYPE , CIM_TYPE , SEND_PORT , SEND_PRTNR_NO , SEND_PRTNR_TYPE , CLIENT , STATUS , CONTROL_RECORD , CHANNEL_ID , ACK_NEEDED , ACK_RECEIVED , ARCHIVE ) values ( ?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,? ) <<: Cannot assign an empty string to a parameter with JDBC type >>VARCHAR<<.
My payload for this message is --
<HU_CREATE01>
 <IDOC BEGIN='1'>
 <EDI_DC40 SEGMENT='1'>
 <TABNAM>EDI_DC40</TABNAM>
 <MANDT>120</MANDT>
 <IDOCTYP>HU_CREATE01</IDOCTYP>
 <MESTYP>HU_CREATE</MESTYP>
 <SNDPOR>SAPPID</SNDPOR>
 <SNDPRT>LS</SNDPRT>
 <SNDPRN>BS_ORIWIN</SNDPRN>
 <RCVPOR>SAPD3S</RCVPOR>
 <RCVPRT>LS</RCVPRT>
 <RCVPRN>D3SCLNT300</RCVPRN>
 </EDI_DC40>
 <E1BPHUHDRPROPOSAL SEGMENT='1'>
 <HU_STATUS_INIT>A</HU_STATUS_INIT>
 <PACK_MAT>000000000002001755</PACK_MAT>
 <HU_EXID>00340042312419076037</HU_EXID>
 <TOTAL_WGHT>11.123</TOTAL_WGHT>
 <UNIT_OF_WT_ISO>KGM</UNIT_OF_WT_ISO>
 <CONTENT>00002059911110071031</CONTENT>
 <PLANT>9610</PLANT>
 <STGE_LOC>2000</STGE_LOC>
 </E1BPHUHDRPROPOSAL>
 <E1BPHUITMPROPOSAL SEGMENT='1'>
 <HU_ITEM_TYPE>1</HU_ITEM_TYPE>
 <LOWER_LEVEL_EXID>00000000000000000000_Test</LOWER_LEVEL_EXID>
 <PACK_QTY>12</PACK_QTY>
 <BASE_UNIT_QTY_ISO>ZCP</BASE_UNIT_QTY_ISO>
 <BASE_UNIT_QTY>ZCP</BASE_UNIT_QTY>
 <MATERIAL>000000000000205991</MATERIAL>
 </E1BPHUITMPROPOSAL>
 </IDOC>
 </HU_CREATE01>
Could you please give me your valuable input for the same.
Waiting for a reply.
Thanks in advance.
Best Regards,
Sugeet.

Hello
Note #1688780 IDoc AAE Adapter fails to insert empty strings in database, has been created to resolve this error. The fix is still being tested, so the note is not available for download just yet. Once the fix is released, the note will be available for download.
Here are some further details on the cause of the error:
The issue occurs if the persistency of the IDoc_AAE adapter is enabled
via the 'Persistance' property for the 'JavaIdocAdapter' resource
adapter and one or more of the IDoc relevant properties (for example
sender/receiver port, partner number or type) of the XI message is/are
empty strings. As empty string insertion into database is not supported
by the persictency framework the above OpenSQLException exception is
thrown and the XI message processing fails.
Regards
Mark

XI Business content for MDM - Syntax error in IDOC adapter

Hi mates,
I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Generated ADRMAS IDOC is
 <?xml version="1.0" encoding="utf 8" ?>
<ADRMAS02>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1" />
<E1ADRMAS>
<OBJ_TYPE>LFA1</OBJ_TYPE>
<OBJ_ID>0000500140</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Swift Transportation</NAME>
<COUNTRY>US</COUNTRY>
<COUNTRYISO>US</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<SORT1>SWIFT TRANSPORTATION</SORT1>
<TIME_ZONE>CST</TIME_ZONE>
<E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
</E1BPAD1VL1>
</E1BPAD1VL>
</E1ADRMAS>
</IDOC>
</ADRMAS02>
Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
Look at the code sample from XSLT mapping program
<xsl:for-each select="IDOC/*/E1ADRMAS">
 <IDOC BEGIN="1">
 
 <EDI_DC40 SEGMENT="1"/>
 <xsl:apply-templates select="."/>
 </IDOC>
</xsl:for-each>
How can an IDOC w/o control record be posted?
Did anyone come across this error? Whats wrong/missing?
I appreciate ur inputs.
thx in adv
praveen

Moorthy,
I tried reloading the IDOC metadata from IDX2. Still I get the same error.
Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
Thanks
Praveen

STO returns with EWM Error "Posting with reference to pur. order only possi

Hi Experts,
We are trying to STO returns GR (161 Movement) with transaction MIGO for a EWM managed plant.
Plant A is a EWM managed plant and Plant B is IM managed plant.
We created a stock transfer order with "B" as supplying plant for plant "A" but with "Returns" tick in the item. (Document type UB)
In the first step, when we try to post 161 movement with MIGO transaction, we are getting the below error
"Posting with reference to pur. order only possible for integrated whse"
Message no. L9510
But the same scenario works between two IM managed plants.
Can you please help me in resolving the issue
Gobinathan G

Hi All,
I am interested in the tail end of this process. I have activated DWM. We have received an Idoc confirming the Inbound Delivery for a Purchase Order Receipt.
The Goods Movement Status of the Inbound delivery has changed to C but there is only a Confirmation of Service in the document flow and the Purchase Order is not receipted.
I am unable to MIGO the PO manually.
I guess the Inbound delivery should have posted a receipt on the PO but not sure what is missing?
Any ideas?
Thanks
Lee

Help Required to post IDOC from R/3 to XI

Hello,
I need help to post IDOC from R/3 to XI
My XI System --- E11 on client 001
My R/3 System -- IXS on client 812
In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 )
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS )
While Posting data from R/3
Recipient Port --- A00020
Recipient Partner No -- RECE
Recipient Partner Type --- LS
Sender Port --- SAPB6M
Sender Partner Number -- B6MTEST
Sender Partner Type --- LS
I am getting error " Could not post IDOC to R/3".
Please let me know where are my setting are incorrect
Regards

In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 ) ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS ) ( Not require in SAP XI)
chenage the PORT NAME IN R/3 it should work.

What authorization required to post idoc from XI via RFC?

Hi all,
I need to post idoc to SAP R/3 system from XI. I have done all the steps correctly. While creating RFC in XI system to connect to the R/3 system, intially I gave my R/3 username and password and tested teh connection. Everything was working fine but when I actually ran the scenario, IDOC was not getting posted in the R/3. But there was no error anywhere.
fianlly after debugging I fould it might be the issue of authorization the the R/3 user i used in the RFC. I then assigned SAP_ALL authorization to my user and posted the iodc again and it started working fine.
Can anyone please tell me what are th exact authorizations/role i need to assign to the r/3 used to use it in RFC and successfully posting the idoc? I dont want to use SAP_ALL authorization in my production environemnt.
Please help.
Regards,
Yash

Hi,
Even i had faced this problem. Whenever I tried to send IDOCs, i used to get an error in SM58, " No authorization to send IDOC of type DEBMDM".
When i got SAP_ALL it worked. However I raised a note with SAP asking for an alternative and this is the reply gave me.
You can get good information on this topic in your online help files.
The following is taken from the document "General Security Measures
(ALE)":
Use the transaction SALE to maintain the ALE configuration, to include setting up the distribution model and setting up ALE user authorizations and profiles. Note the following:
- Be restrictive when assigning the ALE authorizations.
The authorization profile B_ALE_ALL contains the following
authorization objects that are needed for ALE:
Authorizations for ALE
Authorization Description
B_ALE_CGRP ALE Customizing Distribution: Group Activities
B_ALE_LSYS ALE/EDI: Maintaining logical systems
B_ALE_MAST ALE/EDI: Distributing master data
B_ALE_MODL ALE/EDI: Maintaining customer distribution model
B_ALE_RECV ALE/EDI: Receiving IDocs via RFC
B_ALE_REDU ALE/EDI: Generating messages (ex. reduction)
S_PROGRAM ABAP: Program run checks
S_TABU_DIS Table Maintenance (using standard tools such as SM30)
Protect external users and passwords.
For example, for a non-SAP system to send IDocs to a SAP System using transactional RFC, it must also send a SAP user ID and password.
In most cases, the user and password are stored outside of the SAP System. Make sure that this information is not accessible to external systems or programs. (How you can do this is dependent on the system that you have; therefore, you need to refer to the documentation for the system where the information is stored.)
However, I feel assigining the profile S_IDOC_ALL should also be enough. Just try and see.
Regards,
Merrilly

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

EDI: Syntax error in IDoc (mandatory segment missing)

HI all,
Error Message - EDI: Syntax error in IDoc (mandatory segment missing)
Status ID - E0
Message No - 072
Status of the IDoc - 26
Please help me how to solve this issue?
Thanks,
Srini

Hi,
This error normally comes up when the sequence of segments has been disturbed.
For successfully posting an IDOC you need to maintain the sequence of the segments as in WE30.
You can also check which segments are mandatory in WE30 by clicking on the segment name and the pop up that comes.
Thanks,
Manish

All ALE configuration are right, but why errors in idocs?

hi any anybody explains why error are occurs in IDOCs when all ALE setting are ok. please explain any scenario

Hi,
One of the commonly occuring error status - 26(Syntax error in Idoc) Outbound
The reason for the occurence of this error is mostly related to the structuring of the segments in the IDoc, the normal structure should have a parent segment followed by the sub segments but in cases when that fails to happen, the Idoc is in 26 status. For correction of this error goto WE30 and check if the mandatory segment is checked.
status 51(Application Document not posted) Inbound
This normally occurs due to the incorrect data being populated in the segments or it could also be related to serialization.
~Krithika

LSMW:Post IDocs Not Yet Posted

Dear All,
I am facing an error in the last step of generating IDocs with BAPIs.
Post Idocs not yet posted, status is red and status text is application document not yet posted.
Please help me.
regards,
Prosenjit.

hi prosenjit,
some where u have missed activating or saving documents.pls chk once.
thanks
sagar

Error posting Idocs

Similar Messages

Maybe you are looking for