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

Similar Messages

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

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,
<b>it says:
VKORG, VTWEG, SPART cannot be determined for customer , vendor</b>
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.

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

Error while posting IDoc

Hi,
i am getting the following error while posting an IDoc: Program parameters for LS XXXXXXXX 2002 have not been set. Please suggest what can be the possible reason for it and the probable solution.

First ,
check the partner profiles in R3,
i.e. a logical system is defined for XI , particluar Message type is added on inbond side and selected the releavnt messge type and and process code. this is all in WE20.
defining a logical system is in SALE.
then ditribute u r the model in BD 64
once every thing is OK in R3
on PI.
create a RFC destination of type R3 which points to R3 , try remote log-on .
this will be used in receiver chaneel
and check u r receiver chaneel is defined under Business system of R3, and BS refers to same client where partner profiles are defined.
and one of the following should be in place.
check 'apply control record from payload' if ur explictly passing Control record from mapping
otherwise,
check sender service and receiver service in Receiver agreement and select appropriate systems.
Regds,
Suresh

Error in Posting IDoc

Hi All,
I am getting the following error while posting an IDoc from XI to R3 in (SXMB_MONI).
<?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>Basic type ORDERS02 does not exist</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Basic type ORDERS02 does not exist</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Where I should define ORDER02 basic type ?
Can anyone help.
Thanks in Advance
Chemmanz

Hi Chemmanz,
You define your basic type in your partner profile settings, and i think doing the same will solve your problem. Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
I hope this helps you solve your problem.
Regards,
abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

SM 58 error while posting Idoc

Hi
I have installed a Netweaver XI 7.0 recently and have completed postinstallation tasks.
Communication between all XI components (i.e IR, ID and SLD is working.)
I am trying to test an Idoc to File scenario and while posting an Idoc from my R/3 system I am hitting upon this error "No service for system SAPD46, client 800 in Integration Directory".
I have scanned SDN forums and came across note 940313 which talks about the registration of R/3 system on SLD by one of the two methods as below..
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
      Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
      SLD (Business system):
      You can now explicitly assign a business system to this client.
      For more details, refer to the SLD documentation.
      Activities in system ABC (self-registration in the SLD):
      Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
      In system ABC, you can check your configuration with Transaction SLDCHECK.
      Activities in Integration Directory (import business system from SLD):
      You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
      Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
I have performed activities highlighted in BOLD. But still error is same.
My question from XI Gurus is that is there any way to know if the manual step of registering my R/3 system in SLD is sufficient (As the SLD bridge for my R/3 system is not configured and I can not use auto registartion.)
Is there any way to check if the R/3 system is successfully registered.
Thanx
Lovein
Edited by: Lovein Khullar on Sep 17, 2008 11:16 AM

Hi,
I think it is due to basis problem, at ID one of service is not working. Please check below mention link for configuration steps
http://help.sap.com/bp_bpmv130/Documentation/Installation/Configuration_Guide_FP.pdf
Meanwhile check all authorization for IDOC processing, else can't process idoc in XI
For IDOC to FILE scenario follow below steps
1. Define Logical system through BD54 after that assign logical system to client through SCC4 window in R3 & XI systems
2. Define RFC destination through SM59 window in R3 & XI
3. Define Port & partner profile through WE21, WE20 windows
4. Trigger idoc from transaction code or test window through WE19.
5. In XI configure SLD under define Product, Component, Technical & business system, it should be WEB as ABAP type.
6. Import component from SLD to ID window meanwhile import idoc from R3
7. Define target structure according to ur requirement and map accordingly
8. Define ports IDX1 & IDX2 in XI
9. In ID define scenario under import business system and configure steps according to ur requirement. Here IDOC is sender so no need communication channel and sender agreement.
It will work without fail

Error while posting Idoc for customer invoice.

hi,
I m posting Customer Invoice through LSMW using IDocs.
Basic type is FIDCCP02 and message is FIDCC2.
While posting the Idoc I m getting error as:
'Document or line item does not exist for invoice reference'.
I m not getting the error why it is asking for invoice reference because
in FB01 it is not asking for any reference or anything.
In Idoc all the item level values are coming prorperly.
If anybody worked on such issues then please reply.
-Thanx.
-Umesh

Hi Umesh,
Try posting customer invoice through TCode - F-22. There it may be asking for reference number. Generally we post customer invoice by F-22 not from FB01.
If you are getting error you can add reference field in your LSMW it may be mandatory in F-22.
Ashven

Error while posting idoc in the receiving system.

i have processed idoc in the same system( sending and receiving idoc in the same system ) by creating a dummy logical sys and uploading a text file for customer details.The outbound processing is succesful and it shows a status message 3. But duriing the inbound processing it shows status as 51 with error as 'ENTER VALID VALUE'. but when testing using we19 it is posted sucessfully without any error..is there anything that i have to configure to process inbound idoc sucessfully?? can any suggest me the correct method for doing this.. suggestions please..
thanks
vidya sagar

Hi,
you need to make sure that in WE20 inbound processing parameters for you LS is maintained propperly. You need to give correct function module and enter whether IDoc should be processed immediately or IDocs should be collected and processed as batch. Also you may check whether the distribution model (BD64) is maintained correctly for the specific message type in the system for inbound processing.
Regards,
Kai

ALE experts: please help Error in posting idocs

Hi All,
I am posting an idoc from ECC 5.0 to 3.1 I system thru ALE/Idoc methodology.
The partner settings, customer model are set up in ECC 5.0, distributed the customer model and I can see the model in the 3.1I system. The partner settings in the inbound 3.1i is creating some issue when I tested the scenario by sending an idoc from 5.0 to 3.1I. The error status is 63 with message "No partner profile exists for sender LS DEVCLNT300, message type DESADV".
Is it mandatory that the outbound process code is same as the inbound process code. Anyways for me, both the process codes are same but having different funtion modules ONE FOR OUTPUT AND OTHER FOR INPUT both are customized "ZIDOC_OUTPUT_xxxx" AND "ZIDOC_INPUT_xxxxx". I guess this part is creating issue to me. ZIDOC_INPUT_xxxxx is empty which doesn't contains any source code.
The reqmt is very urgent. Any help in identifying the issue will be appreciated
Thanks
Ricky

Hi,
the easiest way is to do it with a distribution model
(even if you don't need it)
create a distribution model in BD64
(sender DEVCLNT300 with message type DESADV)
save it and from there - generate partner profiles
then everything will work
rembmer to check the partner function in We20
(maybe you don't need LS and you have it or the other way round)
but try with bd64 first - it will work
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

SM 56 error while posting IDOC thru XI (File to IDOC) ????

Hi ,
When I am trying to post data into R/3 system thru MATMAS idoc,I have problem in posting data in R/3 system. In XI side the message is sent correctly to R/3 system, but in R/3 it is giving me SM 56 error, while mapping I tried to map only few fields, other mandatory fields I had populated with some constants and values and rest unwanted segments I disabled them. When I saw in error log it says PARTNER PROFILE is not properly set (but I checked Partner Profile is correct), when I checked the record it shows all fields (mapped with constants and values) except the mapped fields.
Can anyone help me in this as I am struggling like anything...
Thanks in advance
Andy

hi Andy,
if you have a problem with control record have a look
at my weblog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Urgent issue: error in posting idocs

Hi All,
I am posting an idoc from ECC 5.0 to 3.1 I system thru ALE/Idoc methodology.
The partner settings, customer model are set up in ECC 5.0, distributed the customer model and I can see the model in the 3.1I system. The partner settings in the inbound 3.1i is creating some issue when I tested the scenario by sending an idoc from 5.0 to 3.1I. The error status is 63 with message "No partner profile exists for sender LS DEVCLNT300, message type DESADV".
Is it mandatory that the outbound process code is same as the inbound process code. Anyways for me, both the process codes are same but having different funtion modules ONE FOR OUTPUT AND OTHER FOR INPUT both are customized "ZIDOC_OUTPUT_xxxx" AND "ZIDOC_INPUT_xxxxx". I guess this part is creating issue to me. ZIDOC_INPUT_xxxxx is empty which doesn't contains any source code.
The reqmt is very urgent. Any help in identifying the issue will be appreciated
Thanks
Ricky

Moorthy is right. Thanks for the help. But my actual scenario is not over by that.
The scenario is a little weird but this is what I need to do.
I want to send idoc from ECC 5.0 to 3.1I and then to external system. I did succeed in sending idoc from ECC 5.0 to 3.1I now but not further to external system. How can I achieve this scenario using ALE. A detailed step by step approach would be helpful and appreciated.
This is what I did and didn't succeed. In the inbound partner profile, I maintained outbound parameters which points to port and RFC destination to external system so that whenever the idoc comes in the 3.1I system it sends the same to external system. I didn't maintain the distribution model from 3.1I to external system which I think worthless. Pls note that I cannot change the architecture in any way. And would like the suggestions to be in sync with the architecture. Thanks a lot and appreciate any help
Thanks
Ricky

Error when posting Idocs From XI to SAP by Partner Profile

Hi all.
i have a problem. all my inbound IDocs in R3 use PP(Partner Profile) LS_XID.
but i need to send IDoc MATMAS by a diferent PP (LS_MATERIALS).
So, i added a new BS in transaction BD54.
In transaction BD64 re-desing the Distribution Model as follow
SL_130 (R3 DES)
> LS_MATERIALS (XI)
|> MATMAS.
In transaction WE20 define the new PP LS_MATERIAL. In inbound table add the MATMAS IDoc. Later imust delete de MATMAS IDoc from LS_XID list. same as transaction BD64.
My problem is when send the MATMAS to R3. it is still using PP SL_XID, so IDoc get status 56 (EDI: Partner Profile Inbound not Available) in R3.
Why?? Any IDea??
Thanks & Regards
Rodrigo.

Hi,
Please check the Logical system,Business system, configurations ,please see the below links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
Regards
Chilla..

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 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

Authorization error in posting IDoc

Similar Messages

Maybe you are looking for