Application document not psted status 51 in ALE/IDOC

Hi Gurus/Experts;
Status number : 51 Application document not psted.
I have configured ALE for distributing material master data. On the outbound side the status of every Idoc is sucess. But on the inbound side some of them are red stating error.
Outbound Side :
we05 t-code.
03 success.
Inbound Side:
we02 t-code.
51 Error.
when I execute the we02 t-code and
Expand Status Record 51
am getting error like : Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT
Please Give me some suggestion on this..
Thanks;
Ravi.

HI jayanth;
thanks for your replay.
we are almost 1 step ahead i think ...
plz suggest me the same...
those steps are very usefull and its cleard the step status type 51 error
now am getting error on inbound side when we execute we02 t-code.
status Error number 29.
Could not determine recipients for message type MATFET
Message no. B1003
Diagnosis
An IDoc of message type MATFET was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Thanks;
Ravi.

Similar Messages

IDocStatus Application document not posted, No status record passed to ALE

Hi,
I am sending CREMAS04 IDOC to receiver system.The receiver system should create vendor entry in master table by using IDOC data.
IDOC is getting posted successfully in R/3,but while calling inbound function module i.e process code CRE1 I am getting following status records :
51 Application document not posted
No status record was passed to ALE by application.
62 IDOC passed to application
Direct call started.
64 IDOC ready to be transfered to application
No filters , No conversion , No version change .
50 IDoc added
Please help me to resolve this problem.

Shweta,
The IDOC has been posted by XI to the R3 system. It is the funtional module that is not able to handle the IDOC and only your Functional Team can tell you why the IDOC is not being processed properly by the R3 system.
It can be because of multiple reasons including invalid data, etc . For instance we once faced an issue once when the User ID used to post the IDOC did not have the authorizations to do financial manipulations and it was our functional team that was able to pin point the reason to us.
Regards,
Bhavesh

IDoc: Status: Application document not posted

Hi Friends,
       I am New to ALE/IDOC. Based on the ALE_QUICKSTART documentation. I have tried to send material from one client to other client. (within system) To do that
I have created two logical systems and assigned them to corresponding clients.
Created a RFC destination and assigned logical systems.
Created Distribution model in sending client.
Created partner profile in both clients.
Created Material and send to receiving system using BD10 tcode.
I checked Idoc status in Sending system, Idoc status is 03-Data is passed to port OK, status 30-Idoc ready for dispatch and status 01- Idoc generated.
But in receving system (Inbound Idoc)- I got status- 51-Application document not posted and Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.
I also checked partner profiles in both systmes- both r same.
Kindly tell me what went wrong and what should i do.
Pl.provide answers pertain to this problem only.
Thanks in advance,
S.Senthil

Hi Chris,
        Thanks for ur reply. I am not using is-retail and I have Generated MATMAS idoc in sending system.
      Kindly provide me answer.
Thanks in advance,
s.senthil kumar

Idoc number have status is 51 Error: Application document not posted

hi friend
i have error in idoc number status 51 Error: Application document not posted. basic type is ORDERS05 Purchasing/Sales
what i do for solve this issue
with regards
dinesh
Edited by: code acess on Feb 9, 2011 4:35 AM

Hi,
{1.how i check in the delivery documents have idoc number ? }
Go into the delivery, output. Check if any output has been triggered for EDI. If yes, then select the output and click on 'Process details' (it is the button just after communication where you give the print name). It will display the Idoc number.
{ what are the required for cofiguration of EDI. Pls Send me the configuration setting . i didnt have help here ..iam expecting configuration setting }
Though it is difficult to share all the config settings in this thread, what I will do is to put in a few steps which are general settings. Only a few things vary.
For EDI / ALE - Idoc the common settings are
a. The port should be enabled for sending and receiving the data thru Idocs. Usually basis does this.
b. Partner profile should be configured in WE20. Example if you are sending a sales order confirmation to ship to party then, You should set up a partner profile in WE20 for partner number in KU (Customer) folder. You can copy any of the existing customer. What you have to make sure is you have added the message type and the Basic Type in the outbound parameters of the partner in WE20. Also, you have to make sure that you are giving the output type and the process type as well.
This is same even when you are receiving the Idocs from customer. Say for example customer PO. However, instead of outbound, you will add all these details in inbound.
Similarly, if you are sending PO to your vendos, then, you have to make changes in folder for partner LS. There are so many other folders as well.
Check WE60/61 for the documentation for what is Basic types, Message types and segments. It is very important for you to know about these when you are dealing with Idocs. To start with, you can give Orders01 in Basic types in WE60 selection screen and read out the details.
c. Once the partner profile is set up, there is a table called VOE4. This is the table where you can maintain the customer cross reference for incoming idocs.
d. Output type should be set up for EDI trigger (Tcode NACE) . You can use the existing programs. You can Check BA00 which is normally set up for EDI trigger as well. You can try triggering that first. You may get some errors at first. But do not panic. Just read those errors and then search the form for errors. You will get to know the next step.
e. Once you have the above settings, I think you are pretty much ready for EDI... you can try these. If you get struck in between, the form is there to help you...
Hope this helps...
Regards,
Mukund S

IDOC is created with status 51( application document not posted)

Hi experts
iam working on File-IDOC scenario, when i test the process the XML message is created with no errors and
but the IDOC is created with status 51( application document not posted)
the details error shows:
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
previously i used same test data that time it was working fine,
please tell me how can i fix the issue.
regards
vasavi

Key in your Idoc number in BD87, execute
select the error message and then follow the menu path :
EDIT --> restrict and process (Select)
In the next screen UNCHECK the Bkgd Processing and execute
Now EDIT --> Process --> foreground from error or in foreground mode.
This will lead you the screen where it errored out.
Thx
PSR

Inbound IDOC error - status code 52- application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

HI
If you are FM to process the inbound IDOC,
possibilities are like below .
Reason 1 :
In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
reason 2 :
If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
reason 3 :
Have you tried with TCODE BD87 , might be it is processing error also .
i have worked on same probelm so if u r not solved with the issue after trying above 3 reasons .
reply me back .

Inboun IDOC status 52--Application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

I am attaching how we documented the process in our troubleshooting guide. Graphics were not pasted.
21.3       Manually run IDOCs reported as 52.
It is possible that IDOCs are found in status 52 for the daily updates.   In principle IDOCs 52 can not be re-proceeed, but there is a way to push the appropriate data from a source system, e.g. ERP.    Following is the process.
21.3.1     You find IDOCs in status 52 in WE02.
21.3.1     Open table EDIDS.
Perform 2 searches for parameter STAPA2 and STAPA1 in status 52 and download the entries for each column to an MS Excel file.
21.3.2     Adjust the MS Excel file.
The strings STAPA2 and STAPA1 have to be truncated and separated into 3 different fields for processing: First 2 characters are the Plan Number, next 2 the Object Type, and next 8 the Object Number.
21.3.3     Manually process the entries via transaction PFAL from the source system, e.g. ERP.
The entries must be processed in the following order sorting by Object Name:
u2022     STAPA2s first, then STAPA1s.
u2022     Each organized by O, S, P, C, and CP.
21.3.3.1     Running individually for each entry.
By running PFAL with the individual entries: Plan number, Object Type, Object Number, Update mode, Target Logical System name ... the respective IDOC will be passed to target system for processing.
21.3.3.2     If there are many entries for processing.
If there are many STAPA2 and STAPA1 for processing.
u2022     Create a text file like the one below with the entries as mentioned above.
u2022     Logon into the source system and make sure CATTs are allowed..
u2022     Via SCAT, create a CATT that emulates the execution of PFAL entering Plan number, Object Type, Object Number, Update mode, Target Logical System name ... the respective IDOCs will be passed to the target system for processing.
. Create the text file with the entries.
. Execute the CATT ... the respective IDOCs will be passed to target system for processing.

BI extraction error -- Application document not posted - IDOC Status 51

Hi,
I am getting the following error while extracting data from ECC to BI.
'Application Document not posted'
I went to BD87 in ECC and found that the Idoc Status is 51 and the message is
'Request REQU_4C65QV...V9QRNZ2X9TV9QRNZ does not exist in target system N05CLNT100'.
I have already checked partner profile parameters with Basis and they claim everything is okay.
Do you have any ideas what might be the issue?
Thanks,

Hello Rajendra,
You can review the note 417307 which contain information about the MAXSIZE of a package size. This is a collective note which contain more notes to other extractors.
417307 - Extractor package size: Collective note for applications
549184 - FAQ: What is important for extraction
157652 - Main memory requirement for extraction from R/3
You can review the table ROIDOCPRMS and check if the parameter StatFrqu contains a 'X' or a number? You can set this option to 99.
You can also review the correction note 1147326.
Check as well if the user ALEREMOTE have the proper profiles configured in both source and target system, sometimes the user is missing the profiles, to check this, read the note 150315.
I hope that the information can help you.
Regards,
Daniel

Request IDoc : Application document not posted

I am loading master data in the development system for the first time after the basline config. I am getting the following error.
Request IDoc : Application document not posted

Hi
Recheck the Connectivity RFC & IDOC too. you may ask basis for help.
verify the IDoc things no problem, connection and authorization between bw and r/3 established well.
try check in monitoring - menu environment
-> 'ale management' - in datawarehouse and in source system.
take a look oss note 520012.
Symptom
RSINFO Idocs with status 51 are repeatedly sent to the top. IDOCs with status 51 (document not posted) queue for ALE inbound processing. This may slow down the system.
Other terms
IDoc RSINFO, status 51, bd87, we05, RSRQST, R3 013
Reason and Prerequisites
The requests are started periodically and cause a R3 013 error message; the message is sent to the BW system but the requests retain a status 51. You can display the IDOCs via transaction we05. Enter RS* in the 'Logical message type' field and execute the process. You can also display the IDOCs with transaction bd87.
Solution
IDOCs with status 51 can be selected for deletion by running the 'RBDMANIN' report; do not use the 'Import in the background' indicator (you must manually remove the indicator).
Each relevant IDOC is then processed separately in the foreground and you can decide for each IDOC if you want to select it for deletion.
Hope it helps

Extended Payment Order with status 51 Application document not posted in IHC

Dear Gurus,
We are make an extended payment order (PAYEXT), through the transaction F110, and then when we want to see the IDOC (by Tx. WE02) we have the following error in the Inbound IDOC´s:
IDoc: 0000000002179110 Status: Application document not posted
Error Message: A transaction type could not be (uniquely) determined - IHC 0308
We enter a payment method and payment method supplement in the proposal on F110.
I don´t know whats the reason of the error. I hope you can help me please.
Kind Regards,

Hi Jayj,
Thanks for your response. Sorry for the delay in responding you
I make the following steps to get the error:
1. I´ve created the invoice through FB60, on the company CO05.
2. IThen I pay the invoice by F110, (I´m attaching the log of the payment).
3. When I want to check by WE02 the IDOC the system generate the error message: a transaction type could not be determine. (I´m attaching the error message)
Please I hope you can help me.
Thanks a lot and kind regards,
Ivan R. Menacho

Inbound idoc application document not posted

Hi,
idoc status is 51 i.e. application document not posted.. when im tyring to send the cm data to other system it is successfull and doing some modifications in that and the same is sent from the other non-sap system to sap system.
During the sending from non-sap to sap system, the inbound idoc is getting the error as 51. and also providing some field name as kna1-cassd is not an input field.
This field is not being provided with any value but still the idoc is getting error with this field.
"Even i tried in the sap system itself, taking some sample data tested in we19 and executing with inbound idoc f.m:IDOC_INPUT_DEBITOR.. still the idoc is getting error message as 51 (with the same field).
Please provide your valuable suggestions to solve this problem.
I had created one cm and tried but still the same message is comming.
Awaiting your help.
thanks
rohith

Thanks for all your suggestions..
The problem is that im using the standard function module:IDOC_INPUT_DEBITOR..
So, this function module cannot be modified which is not my requirement.
My requirement is that i will send an outbound idoc to some non-sap system and now the non-sap system will make some modifications and resent to sap system (here in sap it is an inbound processing).
So, during inbound processing the status is showing as 51 due to the field kna1-cassd..
So i cannot make any customization but the inbound processing should be done and it should be saved into the db...
Hope you have got a clear requirement.
Waiting for your response.
Thanks
rohith

Error "Application document not posted" when tried to receive an idoc

Hi All,
My scenario is File to IDOC. the idoc reaches the R/3, but when i check in the transaction we02, under Inbound IDOCS, i see my idoc in status 51 - Application document not posted.
Does it mean idoc has reached R/3, but it didnt update the respective table in R/3? i'm sending idoc of type MATMAS05, its supposed to update table MAKT, but its not. Do i need to make any special settings for this? pls help me, its urgent.
Thanks & Regards,
Bhavana

Hi,
The IDOC is successfully coming from XI, but there is problem in R\3 end.
Idoc status is 51 with "Application document not posted"
This indicates that the logic for posting the application document is not coded properly in inbound function module. Verify the logic once again.
Also you need to confirm that the data related or in application configuration is right. If the data values are not correct the above error get generated.
refer blow link for the program
http://help.sap.com/saphelp_nw04/helpdata/en/78/21760251ce11d189570000e829fbbd/frameset.htm
Thanks
Swarup
Edited by: Swarup Sawant on Jan 28, 2008 11:13 AM

Idocs statsu 51 Application document not posted

Hi All,
We are having an issue with orders having large number of line items in which Shipping confirmation Idocs coming from warehouse are going to status 51 (Application document not posted) when we look at the status record it shows "Object requested is currently locked by user" . This issue started happening after the ECC 6.0 upgrade.
Please advice for the same.
Thanks

Dear Abid,
Did you try to search the Forum? There are lots of threads regarding this..... Please use the search option of the forum and you will get lots of material which may further enhance your knowledge.
Check this thread....
Object requested is currently locked
Thanks,
Raja

Urgent: Error in idoc(Application document not posted)

Hi experts,
i am getting the error in R/3 side when i am extracting data from it.
i checked with WE07 it's shows the error as follows
"Application document not posted".
it's been urgent how to resolve this issue. please through a light on it.
Regards
Harikrishna N

Hi Hari,
You start error processing by executing the corresponding work items in your Business Workplace. If a file read error could be corrected, for example, the IDocs which have not yet been read can be read and stored in the database manually, by starting report program RSEINB00.
This could be the reason for ur error..
IDoc could not be generated under MC
EDIN: Evaluates the partner data from the MC record
TS70008037
No process code in the additional partner profile MC parameters; Error when writing the application data in the IDoc.
this link givs u the req info
[http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm]
Hope it helps U
Regards,
NR

Request IDoc : Application document not posted ERROR

Hi All,
When I am executing Info Package in BW PROD the system is showing error
Transfer (IDocs and TRFC): Errors occurred
Request IDoc : Application document not posted
I searched the forums but no such kind of error regarding this senario.This problem is for all IP in BW PROD.
Can anyone help in this issue.
Thanks,
Mayur

In SCC4 the following
in we21
Please do not make any changes to these parameters by urself ,ask ur basis team to check it and change it accordingly ....

Application document not psted status 51 in ALE/IDOC

Similar Messages

Maybe you are looking for