Document under "posted status"

Hi
I have posted one document: Document type KR (vendor invoice by using t-code FB60) ....when i check at FBL3N , document comes under posted status instead of open status.My doubt is
a) why document is under posted status. and not under open status.
b) how can i change status from posted to open

Hi
It is showing posted because the vendor invoice document is posted when you have done FB60, but it will be open for payments.
Regards
Sandy

Similar Messages

Document under status posted (T-code FB03)

there are 10 line items on one g/l account , out of which 8 docs are under open item status, and other are under posted status...now my question is
(1) how do we get posted status....under what condition a doucment which comes under posted status ..instead of open status..
(2) how can i clear document with posted status with t-code: F-03
Regards

go to fs00
there is an option of open item managed there. Posted status eg discount is posted to an account. Open item is when you have an invoice which is 'open' You have to pay it.
Points will be appreciated
Regards,
Zaid Azam

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

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

Foreign trade--Posting status of billing document block

Hi,
We have foreign trade set up. In that we defined incompletion schema at line item level with commodity code as "Field ready for input - Incompletion check active".
Can anybody tell me that, in the above setup, can there be a billing block or posting block if commodity code is not maintained in the billing document.
And in which cases Posting status will be "missing foreign trade data" in billing document.
Rajesh.

Hi Rajesh
If you have maintained commodity code as "Feild ready for input",and if you have maintained commodity code feild as error message then it will block the billing document
Generally the posting status will be "missing foreign trade data" in the billing document if the foreign trades data is not maintained in material master record,proper configuration is not done
Kindly check the following link which will help you
http://help.sap.com/printdocu/core/print46c/en/data/pdf/SDFTPRO/SDFTPRO.pdf
Regards
Srinath

Posting Status in Billing Document

Dear All,
How the reason in the posting status of the Billing Document comes ...I mean to say where we do the customizing with these posting status reasons.
Kindly suggest .
Best Regards,
Ankur

Hi
This is Hard Coded by SAP in domain RFBSK, so not a part of standard customising. If you wish you may check the value range of domain RFBSK in Transaction SE11.
Regards
AA

Posting Status in billing document header

Hi all,
In the billing document header we have 'Posting Status'. For example if we won't require accouting document, it says 'Billing document is not relevant for accounting'. Where do we maintain control for this.
Thanks
Sri

Dear All,
In-line with Mr. Muthu's explaination, I would like to add:
It is VBTYP and Account Determination Procedure in Billing Document Type Configuration, which defines the Accounting Document generation.
Say, in case of Proforma Invoice (F5, or F8), you will find:
VBTYP as "U" (Blank) and No Acct. Doc. Deter. Procedure assigned.
Whereas, in case of F1, or F2:
VBTYP as "M" and Acct. Doc. Deter. Procedure assigned.
Important: Check Fields: SD Document category and Transaction group, for F5 and F8 (it would be "U" and "8") AND F1 and F2 (it would be "M" and "7")
Also,
What Billing Document Type would be considered As Cancellation Billing Document Type, would also get considered by VBTYP.
An Invoice, with VBTYP 'M', can only be canceled with Billing Type with VBTYP 'N' .
Note: Check Billing Documents in VOFA.
Very Best Regards,
Amit
I am really Sorry, But I could not Stop myself, to provide my inputs.

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

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

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 status 53 but no document is posted

All,
I am sure this would be answered earlier but not able to find the thread.
Can somebody please let me know, when I process the IDOC using WE16, I get status 53 but dont find document as posted.
Thanks
Sameer

Hi,
Check the config stuff if you are usng the right IDoc...See partner profiles and the message types.
thanks

Error: Application document not posted

hi,
while posting IDOC into R3, I got below error in WE05.
under status records
51 Error: Application document not posted
Account group is not defined in table T077K
reward points always helpful for helpers.
Regards,
Nageswari

HI,
Check the posting program use call transaction, if no analyze the error message and fix the problem. If yes then debug your program step by step until you hit the error screen.
If error in IDoc data , then Exit the IDoc restart from BD87, else problem with application configuration, restart from beginning.
--related Data error contact your Functional team
Also see the below links
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards
Chilla

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

Prevent negative budget after a transfer (pre-post status)

I have a situation where the system allows budget transfers (with insufficient budget) to pre-post using FMBB. The scenario is as follows...
                       Cur      Exp   Avail
FundCenterA     100     50     50
FundCenterB     200     25     175
Although only 50 is available in fund center A, the system allows the user to pre-post a transfer for more than 50 (75 for instance) from fund center A to B.
After the initiator creates the pre-post transfer document, approval of the transfer is attempted by a budget analyst, but the document remains in pre-post status and the analyst can't take any further action.
Can preventing this be accomplished through consistency checks causing the initiator to get a hard error? If so, how or why not? If it cannot be done using consistency checks then what are my choices.

I looked back at note 983853. The last bullet under the solution suggested...
"Create and assign a tolerance profile that contains absolute variances, which triggers an error message for the absolute variance equal to the value 0."
Instead of creating a new tolerance profile which I have attempted in the past, I changed the existing profile to include absolute variances as well as usage rates...and added two separate tolerance limits for activity of posted budget 90 and budget posted provisionally 95 and set them for absolute variance only of the value 0.
Both 90 and 95 had to be changed because...
When only activity 95 is changed for absolute variance, the check document feature (F7) does not detect a negative budget but attempting to pre-post will result in an error.
When only activity 90 is changed for absolute variance, the check document feature detects the negative budget but pre-post will not detect an error and allow the user to proceed.
Therefore both 90 and 95 are needed together.

Document under "posted status"

Similar Messages

Maybe you are looking for