Controlling Document Not Getting Posted

Dear All,
We have a peculiar scenario of Controlling Document not getting posted. Any pointers on wat could be the issue will be highly helpful.
Scenario:
We have an interface which posts an accounting document.
Dr. Expense
Cr. Balance Sheet.
The Cost Center is supplied thru the interface and FI document and Profit Center Document is posted without any issues. However, CO document is not generated, not sure wat could be the issue. We have performed the basic checks. Also, for the same expense account, we observe some postings have gone into CO where are some didnt'. The difference between documents posted with corresponding CO and documents without corrsponding CO posting is only the "Transaction Key". When we maintain blank Transaction key.. the system posts CO document, when transaction key is "WRX" for that specific GL the system doesn't post.
Not sure why Standard SAP behaves like that. Please advice wat items i need to check to resolve
this.
regards
Diwakar

Hello,
Make sure in OBYC, for key WRX, you have maintained the GL accounts.
Regards,
Ravi

Similar Messages

COPA Documents not getting posted - Doc with unauthorized busi.trans SD00

Dear Experts,
COPA Documents are not getting posted, although billing /accounting documents are getting posted
We are getting the below error message, when KE4ST is executed
Kindly share your inputs for this issue
Document with unauthorized business transaction "SD00"
Message no. KE/AD604
Diagnosis
Document 6000000026 cannot be transferred to Profitability Analysis (CO-PA) because the business transaction"SD00'"(Billing document) is not profit-related.
System Response
The document is not posted to CO-PA.
Procedure
If you decide that the document does contain data relevant to CO-PA and that it therefore should be posted to CO-PA, change your Customizing settings accordingly. Otherwise you can ignore this message.
Advance Thanks,
Sanjai

Hi,
   1. First please check if COPA is active in the system i.e. tcode KEKE
   2. Then check if operating concern is active in tcode KEA0
   3. If so then check if billing document has an account assignment to PA segment. If not then maybe you have changed the account assignment in OKC9.
   4. If all the 3 conditions above are satisfied then you need to check if this is a made-to-order scenario (MTO). A made-to-order scenario can be identified in COPA in that the billing doc will have an account assignment to a sales order in addition to a
PA segment (field vbap-kzvbr = 'E' and vbap-vbelv = sales order no).
If the above conditions are satisfied then from a COPA point of view it is a MTO. In this case the invoice will be assigned to the sales order and will not be directly transferred to COPA. With the order settlement the costs and the revenues (invoice) will then be posted to COPA.
regards
Waman

Material Document not getting posted.

Hi Guys:
Material document is not getting created when i try post the inventory difference using transaction LI21 ( Clearing of differences in Inventory Management ).
we are using WM , so physical inventory is carried out at Bin Level.
Did I miss anything in the config setting?
Thanks
Sweth.

Hi Jurgen:
do you have a pick or putaway quantity in this quant in storage type 999 ?
Yes , in the available quantity I could see the -ve quant ( Goods Issue/Pick) and + Quant (Goods Receipt/Putaway)
is the quant locked?
Quant is showing with unlocked logo.
is somebody else in change mode in that quant?
Nope
is this the only item in your inventory document?
yes
have you tried to execute LI21 in background?
I don't how to do that ,
do you require to enter a reason for the difference?
I didn't see that question Popped Up.
Thanks for the help.
Sweth

Document not getting posted to G\L account

when i try to release the document to G/L account using vf02 by clicking flag getting error msg : account 800000 requires an assignment to CO object & when i use t-code vfx3 in the log file the msg is incomplete due to FI/CO interface now how to proceed further to post the doc to G/L account pls guide

Please speak to your FI Consultant.
He will assign a relevant Cost Element the GL A/c Number 800000 in T-Code FS00 (Under Edit Cost Element Button).
Hope this helps.. .
Thanks,
Jignesh mehta

Profit centre document not getting posted in ledger 8A

Hi All,
We are posting a a document through FB01. We have given a profit centre & also derived a profitablity segment. After the FI document is posted, when we go to environment>Document environment>Accounting document we are double clicking on profit centre document. It is leading us to a screen which shows that the ledger is L0 but we want 8A to appear. What are we missing?
Thanks,
Lakshmi

Please check the ledger to application/sub application assignment in table T881.
You should normally 8A ledger - Summary table GLPCT - Application EC - Sub application PCA.
Regards,
Ganesh

Error while posting payroll results to FI - Documents not getting created

Hi all,
While posting payroll results to FI for Dec 2011 a failure of our Production Server resulted in erroneous posting of payroll
results. Posting run no: 1756 did not get posted at all though the run
status shown was "document posted". The issue was resolved by resorting
to manual posting of entries.
Now we are unable to post payroll results for Jan 2012 for the same
range of employee numbers for whom the manual posting was made for Dec
2011. No posting documents are getting created.
Kindly suggest how to resolve the issue.
Regards,
Sunil

Hi All,
I raised an OSS for the issue. SAP Support provided a solution for the problem. The solution involved cancelling a reversal which we had tried and failed followed by re posting the run no 1756. Our manual entries had to be reversed.The solution is given below.
Please follow these steps:
- Select the posting run 1756
- Menu => Edit => Reversal => Reset after termination
- After last step the status of the posting run should appear as
'documents posted'
- Go to transaction SM13
- Select by user 8273 and date 02.01.2012
- You should see an entry like this:
400 8273 02.01.2012 15:26:57 @07\QEnqueues released@ Error
- Select the entry and press the button 'Single test'
- In case the system shows an error, please send the message back to us
- In case the system shows no errors => press button 'Repeat update'
- Then check in PCP0 and FI is the document has been correctly posted.
Regards
Sunil

Profit Center Document not getting generated when direct FI doc is posted

Dear Experts,
Profit Center Document not getting generated when direct FI doc is posted. However CO Document is generated for Line Item 1 mentioned below.
Accounting Entry
Line 1 -Debit Expense ( Cost Center) 1000
Line 2 - Credit Bank 1000
Advance Thanks
Sanjai

Hi,
Pls check profit center configuration.... Some config might have missed.....
Use the t.code 1KE1 For analysing the profit center configuration.
Regards,
RAM
Edited by: Ram000 on Oct 7, 2011 10:45 AM

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

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

52 Application document not fully posted

Hi
I am using IDOCS and after output,this is the status of the IDOC:
52 Application document not fully posted
How can i see where the status is set in order to fix this warning and get a green status?This is an input idoc
Thanks

Solved it by myself,data read from the db was not correct

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 .

CO-PA document not getting generated

Hi,
while sales billing CO-PA profitability document is not getting generated. I have checked the configuration. In
KE4I the condition type (with account key ERL) has assigned to the value field ERLOS.In PA transfer structure
we have maintained the assignments - source and value fields, here included the sales revenue GL which has the
cost element category 11.
In the sales order we have account assignment with real WBS object. Is this hinders the profitability document
getting generated?
while VF01 system is not generating the profitability document but accounting and controlling document
is getting generated.
Is it mandatory to mention the Business area in KEDR derivation?
Requesting a early feedback.

Hi Mel,
Since WBS is assigned to the order item, both revenue and cost will be collected in WBS if the WBS is marked as 'billing element'. Check the WBS master to confirm this.
The COPA document will be generated when the WBS is settled after RA run.
Otherwise, check in KE4W, if COPA value flow has been reset for your billing type.
BR
Abhinav

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

In EBS document not get auto clear Algorithms 11

In Electronic bank statment document not get clear automatically while batch run.
I update check no to payment document. even though it is not get auto clear.
in OT51 assign Interpretation Algorithms 11 011:(Outgoing check: Check number not identical to document number)
why it is not get auto clear with check number.

011 = Outgoing check: Check number not identical to document number
012 = Outgoing check: Check number identical to document number
The "document number" in the descriptions is the payment document number - the FI doc that cleared the invoice. If you use the payment document number as the check number - and thus that is the number the bank includes in the bank statement - then you would use algorithm 012. If you create a check in the check register that is a different number than the payment document - and the check number is the number in the bank statement - then you would use algorithm 011.
Search SAP Help for a document titled "Interpretation Algorithms". This document includes descriptions of all the standard interpretation algorithms.
Regards,
Shannon

Controlling Document Not Getting Posted

Similar Messages

Maybe you are looking for