Idoc not getting post

Hi Friends,
i am using transaction WPUK , there if i enter eann number starting from 1, for ex. 1WMDP000023 Then idoc posted but
if i enter eann number starting from 0, for ex. 0OA103403929908 , idoc not gettign post , error is eann number not exist or not maintained against the material number, but i have already maintained via MM42 in basic view.
pls suggest what i should do, i am already debugging but can't resolve it.

Hi Medha,
Give the leading zeros and check.
Regards,
madhu.

Similar Messages

Plz Help:Idoc not getting posted

In my requirement some of the idocs are not getting posted.The error message is "Balance not zero".Idoc type is "INVOIC01".In my requirement they told to look into the standard sap pgm"SAPLMRMC" in that FM MRM_AMOUNT_COMPARISON.Please give me suggestions to proceed.

Hi Hema,
Please check the invoice data that your are trying to send. From the error it seems that the IDoc is failing the data validations that must be placed in the program/FM that is used to generate/post the IDoc.
Regards,
Ashwinee

Idoc not getting posted into XI

Hello Experts,
I am trying IDoc-XI-File senario...
I have configured, ALE on backend system. Configured IDX1 and IDX2 in XI system.
At sender the Idoc has been sent without any errors.
But when I check in XI using SXMB_MONI there are no messages. Idoc is not getting posted into XI.
Please suggest as I am struck at this point. I am using XI 7.0
Thanks
Suma

Hi,
Kindly verify the ALE steps that you have performed...
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 7)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful...
PrasHaNt

IDOC not getting posted into BPM

Hello Friends,
I have a scenario where i am using Async/sync bridge in BPM to convert an IDOC message into webservices.
I have configured the BPM correctly without any sematic errors.
Whenever I post an IDOC, i get an error message saying - "Party and service not defined"
Do I need to "START" a BPM from somewhere??
Im getting stuck at the starting itself
Please help me friends!
Regards,
Lakshmi

Hi,
in ID, in your R/3 business system, from menu go to Adapter specific identifiers......then a popup window will come.......then in that window, your logical system for IDOC may be blank.......click on Compare SLD button at below, then your logical system field should be filled with the logical system you have defined for your r/3 system in your SLD.
Then again send your IDOC from r/3 to XI.
Regards,
Rajeev Gupta

Idocs not getting posted from XI to R/3

Hi guys,
We have set up a file-to-Idoc scenario that seems to work fine, but when the number of idocs to be posted in R/3 reaches a certain number, (3,500) all idocs are getting rolled back and nothing happens in R/3.
It seems to me that there should be a parameter to set this up.
Any ideas?

Hi,
report RSEOUT00. To determine the package size, specify the maximum number of IDocs.
The number of IDocs in a file is specified by the parameter Maximum number of IDocs in the program RSEOUT00.
see SAP Note 814393
Please refer
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b
Example Program for Mass Processing IDocs
http://help.sap.com/saphelp_nw04/helpdata/en/78/21760251ce11d189570000e829fbbd/frameset.htm
Thanks
Swarup

Idoc not getting posted

Hi All,
We are posting the Business partner data from HR to CRM through Idocs. Though we are able to get almost all the Business Partners in CRM, one of the idoc is showing the message 'Application document not fully posted'. When i checked the status record it says that:
Message no. HRALX00_ORG246
In order to further process business partners, the system must determine the internal keys for the business partners. An error occurred when trying to determine these keys.
The error occurred in function module RH_ALEOX_BUPA_WRITE_O when calling BUP_PARTNER_GUID_CONVERT (error code 2).
If you have any inputs regarding the error, please help us.
Thanks & Regards,
Rahul.

hi,
go to the RFC destination that you use
to post IDOCs (from receiver IDOC adapter) - transaction SM59
and go to it's logon/secutiry tab
and check if the user which is defined over there
has the right authorizations to post idocs in R3
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>

IDOC Not getting Posted in PI from CRM

HI All,
I had Configured,
in CRM side : SM59,WE21,BD54,WE20
in XI side: datatypes,MT,MI, Maaping not yet done, IDX1,SM59
Idoc is not getting displayed in XI system.
I had a small Question, Do we need to Configure all the setting in XI for Getting IDOC from CRM.
Thanks in Advance,
Sriram.

Hi Jag,
Thanks for the reply.
1.CRM: go to Tcode-WE81 and check message type CRMXIF_PARTNER_SAVE created?
Yes exists
2.CRM: Execute Tcode-WE82, Check message type CRMXIF_PARTNER_SAVE has relevant IDOC type and version.
yes both message type and basic type exists
3.XI: Did you import right Message type and IDOC type in to IR in XI?(name will be like Message_type.IDOC type)
yes imported CRMXIF_PARTNER_SAVE.CRMXIF_PARTNER_SAVE01 in IR.
When i see in Table EDMSG in XI system i am not finding the value CRMXIF_PARTNER_SAVE, but this value Exists in CRM system
in XI i m not finding the message type in WE81 and WE82.
Thanks in Advance,
Sriram

Inbound Idoc not getting posted

Hi,
I am facing a problem in posting an Inbound Idoc of Baisc type INVOIC02 and Message type INVOIC.
The Idoc stays in status 51 and the error is "Function Code cannot be selected".
I have checked the Function module, it is already assigned to the process code.
Please help me.
Thanks in advance.
Regards,
Rachit.

Hello Kristine,
I'm "afraid" to make any suggestions if you say you have checked the ALE configuration more than 3 times....
However the message you are getting suggests the client specified for the partner system is not correct. If you double click on the Target system in the overview of transaction SM58 you will go into the RFC destination; is the client specified there really ok?
If all is ok you might you in the debug mode: Copy the transaction id from the overview and goto SE38. Put a break-point in program RSARFCSE (if you don't put a break-point before you execute you will have a hard job to get there because it is a system program). Then start the program using the transaction id and set 'Forced'.
Regards,
John.

Idoc not getting posted in R/3

scenario - file to idoc
This Scenario is now executing properly and in SXMB_Moni it is also showing new generated IDOC number.
But when I tried to locate same IDOC in R/3 system i am not able to locate it.
In IDX5 tcode is showing error msg - "No authorization to send IDocs with message type ZTEST".

hi,
go to the RFC destination that you use
to post IDOCs (from receiver IDOC adapter) - transaction SM59
and go to it's logon/secutiry tab
and check if the user which is defined over there
has the right authorizations to post idocs in R3
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>

Inbound IDOC not getting posted in database

Hello All,
I have a similar problem below:
http://www.sapfans.com/forums/viewtopic.php?t=59840&highlight=inboundaleconfiguration
Currently, I have distributed exchange rates from my sending system to my receiving system. When I check on the IDOC status, it is set to status 03 (Data passed to port OK) but on the receiving system, I am unable to find any IDOCs received.
I have checked more than 3 times the ALE configuration and I'm really stuck now.
I have already looked in to tRFC Queue (SM58) but I don't know how to trace the errors. The message I'm getting in SM58 is "Client M88 is not available. Please choose an existing client." However, I tested the connection from the sending system to the receiving system and it works OK.
I'd appreciate any help.
Regards,
Kristine

Hello Kristine,
I'm "afraid" to make any suggestions if you say you have checked the ALE configuration more than 3 times....
However the message you are getting suggests the client specified for the partner system is not correct. If you double click on the Target system in the overview of transaction SM58 you will go into the RFC destination; is the client specified there really ok?
If all is ok you might you in the debug mode: Copy the transaction id from the overview and goto SE38. Put a break-point in program RSARFCSE (if you don't put a break-point before you execute you will have a hard job to get there because it is a system program). Then start the program using the transaction id and set 'Forced'.
Regards,
John.

FI - Interface triggerring multiple idoc is not getting posted

Hi all,
I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
But the same idoc, when i proccess indivisually get's process gets posted successfully.
I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
As an abaper, I am not able to understand problem to take corrective steps.
Thanks & Regards
shashikant

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

EDI vendor invoices do not get posted before GRN is posted

Hello All,
The requirement is our vendor sends EDI invoices and they get parked in SAP as IDOCs. IDOC gets posted if GRN exist for a PO.
In purchase order it is GR based IV. If vendor parks invoice and there is no GRN for purchase order then IDOC fails and it goes in status 51 (Error).
Our requirement is, IDOC should get posted even if there is no GRN for a purchase order and client do not want to remove GR based IV tick from PO. After through verification of the parked invoice it gets posted in the system.
We have done the config change in MM>>LIV>>EDI>Enter program parameters, we have maintained value "1" for field "Processing". Inspite of this change system does not process inbound ICOCs and they go in error (51) status.
Please provide solution for this.
Thanks & regards.
Sanjay

Hello Jurgen,
The change in piece of code suggested in SAP note no. 501524 was already implemented in our syste, However still invoice IDOC fails and it goes in error "status 51" as there is no GRN for that purchase order. However if material GRN is made for 1 qty then the invoice gets parked with the full amount even if the GRN is for 1 no.
Please suggest a suitable solution.
Thanks.
Sanjay

Data is not getting posted in ABAP Proxy.

Hi,
I am working on File to ABAPProxy scenario. The data is not going to proxy.
In PI sxmb_moni is status is successfull and in the R3 sxmb_moni the status is successfull. But the data is not getting posted in the tables(ABAPProxy). I had checked the inbound and oubound queues. And with the same input data, abapers cheked their code in Abapproxy, then the table is getting updated. When we trigger from PI, the tables are not getting updated.Please help me.
Thanks,
Pragathi.

Hi,
The problem may be
Case 1: Cache is not getting refreshed(Check SXI_CACHE)
Case 2: The Queue Is blocked (Check SMQ1 & SMQ2)
Regards,
Sainath

Invoice is not getting posted to accounts it is showing the export error

invoice is not getting posted to accounts, it is showing an error of foreign trade / export data. where as it is with in the country. it is maintained for the plants abroad stock transport order.

A stock transport order to a location overseas etails crossing national borders and change of legal regulations. hence you need to maintina FT data. Please check the FT data in the billing header and item and maintian them. They are simple items like customs offices meas of transport...
This will give you a green status from the red status you will initially have. Then you can post the invoice.
regds

Files are not getting posted in destination directory,how to trace in XI

Hi,
our scenario is proxy to file.
We are posting files of .TRG and .DAT format in destination directory.Due to less space in destination directory, files only .TRG files are getting posted but .DAT are not getting posted.but i have checked in XI system SXMB_MONI,no error message is coming.message is getting processed successfully.
why it is not visible and to monitor that files are not saved at the destination.
Is this normal with XI that we can not see of files are really saved?

Hi,
> it should generate two files as per scenario but only one file is getting generated due to less space,
NO.
If No Space, The error will pops out in RWB .
Check the directory of the File Adapter you are using
Regards
Agasthuri Doss

Idoc not getting post

Similar Messages

Maybe you are looking for