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.

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 purchase order delivery

Hi
I got an error while posting purchase order delivery through Tcode- MIGO
This is the Error Message:
Posting only possible in 2009/04 and 2009/03 in company code XXXX
I checked everything Fiscal year variant,Posting period variant,etc.
And in Tcode- OMSY.
Let me know as early as possible how to solve this issue.
Thanks and Regards,
Deepthi.

Hi Deepthi,
You need to understand that posting periods 3 and 4 does not necessarily mean march and april in SAP.
Check your fiscal year variant for the months which correspond to periods 3 and 4. Then you will be able to solve your problem by yourself.
Open and close periods in FI - OB52
Close periods and open new periods in MM Side - MMPV
Hope this helps you....
Regards,
Sreekanth....

Statistics Currency Error while posting Sales Order (No: V1453)

Hi Sappers,
I am in process of making a company in SAP ERP SD - IDES, and while posting Sales Order, after I input Sold to Party, PO no, Del Plant and Incoterms and I press ENTER: The error comes up as:
Statistics: The currency from in INR for date 25.11.2011 could not be determined.
Kindly suggest a possible solution.
Thanks
Rahul Tikku

Hi,
Just go to "OBD2", select the Accounts group of your customer and "Double Click" on it, then "Double cliick" on "Sales Data" > Further goto, "Sales" and check if "Currency" field is suppressed. if so then change it to required or optional Entry. save and update you customer master in XD02. Then try your process.
Reagrds
DSR

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

Va01:errors during posting sales order

Hi there,
can anyone help me on the error log during posting sales order via va01? the checking of sales order is correct.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          2009.02.17 10:11:37
Short dump has not been completely stored (too big)
|Short text          |
|    The current application triggered a termination with a short dump. |
|What happened?      |
|    The current application program detected a situation which really   |
|    should not occur. Therefore, a termination with a short dump was    |
|    triggered on purpose by the key word MESSAGE (type X). |
|What can you do?    |
|    Note down which actions and inputs caused the error.   |
|       |
|       |
|    To process the problem further, contact you SAP system |
|    administrator. |
|       |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look         |
|    at and manage termination messages, and you can also   |
|    keep them for a long time.   |
|Error analysis      |
|    Short text of error message: |
|    Maintain the current CRM release (table CRMPAROLTP)    |
|       |
|    Long text of error message: |
|     Diagnosis      |
|         Various transfer errors occur when transferring SAP sales orders to         |
|         CRM or there is no status update or the status update has errors            |
|         when transferring from CRM to the SAP system. This is caused by an          |
|         incorrect entry for the CRM release in the SAP table CRMPAROLTP, or         |
|         no entry is maintained at all.       |
|     System Response|
|         To avoid data inconsistencies, this message causes a short dump.            |
|     Procedure      |
|         Maintain table CRMPAROLTP in your SAP system as is described in SAP         |
|         Note 691710 and then repeat the process again.    |
|     Procedure for System Administration      |
|       |
|    Technical information about the message: |
|    Message class....... "V3"    |
|    Number.............. 302     |
|    Variable 1.......... " "     |
|    Variable 2.......... " "     |
|    Variable 3.......... " "     |
|    Variable 4.......... " "     |
|How to correct the error         |
|    Probably the only way to eliminate the error is to correct the program.          |
|    - |
|       |
|    If the error occures in a non-modified SAP program, you may be able to           |
|    find an interim solution in an SAP Note. |
|    If you have access to SAP Notes, carry out a search with the following           |
|    keywords:       |
|       |
|    "MESSAGE_TYPE_X" " "         |
|    "SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"           |
|    "BAPIDATEN_ERMITTELN"        |
|       |
|    If you cannot solve the problem yourself and want to send an error |
|    notification to SAP, include the following information:|
|       |
|    1. The description of the current problem (short dump) |
|       |
|       To save the description, choose "System->List->Save->Local File |
|    (Unconverted)". |
|       |
|    2. Corresponding system log |
|       |
|       Display the system log by calling transaction SM21. |
|       Restrict the time interval to 10 minutes before and five minutes |
|    after the short dump. Then choose "System->List->Save->Local File   |
|    (Unconverted)". |
|       |
|    3. If the problem occurs in a problem of your own or a modified SAP |
|    program: The source code of the program   |
|       In the editor, choose "Utilities->More |
|    Utilities->Upload/Download->Download".    |
|       |
|    4. Details about the conditions under which the error occurred or which          |
|    actions and input led to the error.       |
|       |
|User and Transaction|
|    Client.............. 200     |
|    User................ "SAMSON"|
|    Language key........ "E"     |
|    Transaction......... "VA01 " |
|    Program............. "SAPMV45A"           |
|    Screen.............. "SAPMV45A 4001"      |
|    Screen line......... 65      |
|Information on where terminated |
|    Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN". |
|    The main program was "SAPMV45A ".         |
|       |
|    In the source code you have the termination point in line 338       |
|    of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".            |
|Source Code Extract |
|Line |SourceCde     |
| 308|    else.     |
| 309|*-----Nicht unterstu9EF7zt, Abbruch        |
| 310|      message a301(v3).    |
| 311|    endif.    |
| 312| endif.      |
| 313| |
| 314|*-Szenario A pru9EE4en        |
| 315| if lv_scenario_a   = 'A'.|
| 316|    vbak-vbkla+2(1) = lv_scenario_a.    |
| 317| endif.      |
| 318| |
| 319|*-ermitteln CRM-Release    |
| 320| call function func_name |
| 321|        exporting          |
| 322|            i_paraname = 'CRM_RELEASE' |
| 323|        importing          |
| 324|            e_parval1 = lv_parval1.    |
| 325| lv_release_crm = lv_parval1+0(3).     |
| 326| |
| 327|* If lv_release_crm empty => X-message (correct download not possible)         |
| 328| if da_download_active = charx.        |
| 329|    CALL FUNCTION 'CRM_CONNECTED'       |
| 330|     IMPORTING|
| 331|       CRM_CONNECTED       = lv_crm_connected        |
| 332|     EXCEPTIONS            |
| 333|       NO_CRMRFCPAR        = 1          |
| 334|       OTHERS = 2          |
| 335| .            |
| 336|    IF sy-subrc = 0 and lv_release_crm = space and   |
| 337|       lv_crm_connected = charx.        |
|>>>>>|        message x302(v3). |
| 339|    ENDIF.    |
| 340|   endif.     |
| 341| |
| 342|*-Fu9EEElen der View fu9EF5 das Ermitteln der Auftragstabellen          |
| 343| da_sales_view-partner    = charx.     |
| 344| da_sales_view-sdcond     = charx.     |
| 345| da_sales_view-sdcond_add = charx.     |
| 346| da_sales_view-contract   = charx.     |
| 347| da_sales_view-text       = charx.     |
| 348|*-bei mehr als 1000 Belegflusssu92DEzen werden Daten nicht ermittelt |
| 349| if lv_tabix_vbfa < 1000. |
| 350|    da_sales_view-flow     = charx.     |
| 351| endif.      |
| 352| da_sales_view-billplan   = charx.     |
| 353| da_sales_view-configure = charx.     |
| 354| da_sales_view-credcard   = charx.     |
| 355| |
| 356|*-Im Standardszenario soll eine manuelle u818Ederung eines CRM Belegs|
| 357|* (ab CRM Release 30A) nicht zuru9EDEk ins CRM gesendet werden. Das |
any responses will be awarded,
regards,
samson

Hi,
Maintain the current CRM release.
The dump might have occurred when transferring SAP sales order to CRM.
This has caused a error in SAP table CRMPAROLTP .
Go to SE91 provide the message class & message number, then click where-used-list & select the program check box.It will show you the program name MV45AF0B_BAPIDATEN_ERMITTELN.
Just check the program with the ABAPer.
Hope this helps.
Regds.......
Sumit

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

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.

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

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 in posting - Internal Orders

Dear Forum,
The users are trying to post the FI Document with the orders entered in the order field. However, the system does not allow the postings and gives the error message - FI Posting not allowed (Order xxxx).
Could you please advise what needs to be checked in the system to resolve the error. The users are new in using the concept of Internal Orders.
Thanks for the help!
Regards
Moderator: Please, search SDN

Hi
You need to release the order in order to solve this issue.
Go to KO02 and enter the internal order number. Go to the control data tab. Clikck on the release.
And now try to post the document
~THanks
Rajesh

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 in posting IDOC ORDERS.ORDERS05

Similar Messages

Maybe you are looking for