Why Documents are not releasing to Accounting Automatically?any reason?

Hi,
Is there is any reason that these documents are not automatically being passed to accounting.Please help me to fix this issue.
Thanks
Supriya

Hello,
This is not just FICO consultant issue.
If you do not have sufficient configuration in VKOA, it cannot be generated.
If you have closed the period in FI, obviously the entries will not be posted.
If the user is not having authorization, obvisouly it fails to generate accounting documents.
There is no special configuration, but this is system behaviour. If something is not available, then it cannot generate the entry.
Hope you have gone through the points mentioned by me.
Regards,
Ravi

Similar Messages

Output to be blocked for Billing documents, if not released to Accounting

Hi SAP Gurus,
We have a requirement, where the Billing documents should not be issued output, if they are not released to accounting.
The system should not allow the user to issue output for billing documents, if not released to accounting.
Regards,
sree.

Standard routine 62 should be able to suffice your requirement.
Provided output determination in billing doc should happen from output condition record (VV31).
If you manaully assign assign output type in billing doc, then system will overlook the requirement.
In addition to that if your output type is assigned with requiremrnt routine 62 in your output procedure.
Then till your release tke billing doc to accounting, you will not be able see output type determine in billing doc.
If you have doubt, whether the output type is getting determined properly or not.
Then output(header/item) screen in your billing doc(VF02), in menubar select Goto - then choose Determin. Analysis.
It will show message that due requirement 62, output determination didn't too place.
Regards
JP

Billing Document is not released to Account -Error

Hi,
I am getting the below error while releasing the billing document into accounting.kindly help me
Error Log
             0900000165 000000 Document 0900000165 saved (no accounting document generated
             0900000165 000000 Enter a true account assignment object with revenues
            Long txt
                Detail
                 Diagnosis
                     You made an account assignment for 420100, a revenue
                     element, in controlling area 9000 to a cost center or
                     profit center.
                 System response
                     Cost centers and profit centers can carry revenues in the
                     R/3 System as statistics only. To ensure reconciliation
                     between FI and CO for revenue element 420100, a CO account
                     assignment object must record the revenues as a real value.
                     This object type is used for updating to the reconciliation
                     ledger.
                     In principle, it's possible for the R/3 System to
                     automatically derive this CO account assignment object, the
                     reconciliation object. However, all postings made in CO for
                     costing-based Profitability Analysis are logged in the
                     reconciliation ledger under "reconciliation object". In
                     this manner, the reconcilation ledger identifies the exact
                     values flowing into the operating profit. If you post
                     reconciliation objects during revenue postings to cost
                     centers or profit centers, you must do so while keeping the
                     interpretation of the reconciliation ledger reports in
                     mind. The sums of revenue postings to profitability
                     segments, cost centers, and profit centers cannot be broken
                     down further.
Procedure
    o   To avoid posting to reconciliation objects, make
        account assignments to a real CO account assignment
        object.
    o   If you want to post to reconciliation objects, you can
        change this message to a caution or a note for future
        users, or deactivate the message entirely. Use the
        Implementation Guide under "Controlling: General" and
        choose Change message control. Enter area KI and
        message number 166. If you do not enter an individual
        user here, the change is valid for all users.
Technical data
    Tech. data details
     Client
     Group Number
     Sales Document Number                  0900000165
     Item Number of the SD Document         000000
     Schedule Line Number                   0166
     Counter in Control Tables              00
     Message Identification                 KI
     System Message Number                  166
     Output Type                            E
     Message Variable 01                    420100
     Message Variable 02                    9000
     Message Variable 03
     Message Variable 04
Please help me
Thanks
Supriya

Hi Supriya,
The following step is missing in your configuration: So please check the following step:
Financial Accounting (New) - Financial Accounting Basic Settings (New) - Ledgers - Real-Time Integration of Controlling with Financial Accounting - Account Determination for Real-Time Integration - Define Account Determination for Real-Time Integration
The above step is used for:
You define account determination for the real-time integration of Controlling (CO) with Financial Accounting (FI).
You have two options for the definition of account determination:
Account determination without substitution (standard account determination)
The level of differentiation with which you want to trace the postings to Financial Accounting determines how many accounts you create and whether you assign transactions or object classes. You can assign the accounts as follows:
You specify an account for all reconciliation postings.
You assign an account to each business transaction.
You assign an account to each object class.
You assign an account to each transaction and to each object class.
Account determination with substitution
In addition to account determination without substitution, you can determine the reconciliation account using substitution. For this, you have to define account determination at least for the specification of the posting key. Furthermore, you can use substitution to refine account determination.
In contrast to when the reconciliation ledger is used, additional fields are available when real-time integration is used:
RCL_ICCF-BEKNZ
RCL_ICCF-RSEGMENT
RCL_ICCF-SSEGMENT
These fields are only filled by the system when real-time integration is used.
Caution
If you deploy the following functions, you may not use the additional fields in account determination:
You still use reconciliation posting instead of real-time integration.
You use real-time integration but you still have the reconciliation ledger activated so that you can use the reconciliation reports from Cost Element Accounting, such as CO/FI Reconciliation in Company Code Currency.
These functions use the reconciliation ledger data, which does not contain the additional fields.
For more information about defining account determination, see Define Adjustment Accounts for Reconciliation Posting.
Please let me know if you need more clarification
Thanks & Regards,
Venkataraju Khottari

Billing documents should not be created when it is not released to accounti

Hi SD gurus,
In some situation, billing documents are generated but it is not released to accounting which results in mismatch between FI value and SD value. We go to VFX3 and see the list of billing documents and take corrective action.
Our requirement is that the billing document should not be generated when system is not releasing this billing document to accounting.
Please suggest a solution for this.
Regards,
Senthil.

Thanks giri.
For the following reasons, the billing documents are not released to accounting.
1. If the user wrongly chosen the billing type for the delivery.
2. After creating condition type, it has to be assigned in COPA. If we forgot to do it, billing doc will not released.
Our requirement is that if the billing document is not able create accounting document, the billing document itself should not be generated.
Hope this will be suffice to understand my issue and suggest a suitable solution.
Points will be rewarded.
Regards,
Kumar.

Billing Document Not releasing to Accounting because of Condition Type

Hi,
We have used Sales Condition Type ZSCM(Which is a statistical condition type) in Billing Documents and they are already released to Accounting.Today we have created one more Billing Document with same Condition type ZSCM.But this billing document is not getting released to Accounting?
What could be the reason? Why it was released to Accounting before with the same condition type ZSCM and why it is not getting released to Accounting this time.
I am breaking my head to find the possible reasons...kindly help me out to find the problem.
1.Billing document 90005889 - has value 64.48462- and It has only 2 Items and it was released to accounting
2.Billing document 90005729 - has value 217.87960- and It has only 21 Items and it was not released to accounting and asking to activate +/- sing in KE4I transaction for the ZSCM condition type.
Why billing document 90005889 is released for accounting and why 90005729 was not released to accounting?
Thanks
Supriya

Hi,
There can be following possible reasons fo the samed :
1. If the specific GL account is not getting any assignment to CO object.
2. Also you need to check assignment with VKOA that whichever GL is assigned as per business process of Sales (the account which is going to be credited) and all relevant settings in VKOA.
3. Pls check all substitutions and validations if any connected with that condition type and GL. Becuase sometimes it may happen that because of calling some other application (for ex. Set or substitution as generally transportation of this element happen with entire hierarchy if you add your substition in the node.) at he time of posting of billing document. This has already happen with our business scenario.
4. Also check if this sales revenue GL is assinged to any set and if that set is called through any substitution ot validation.
Pls check all these possibilities and revert.
Thanks & Regards,
Taral Patel

Invoice Document not released to Accounting -Period was closed

Hi,
SD Invoices are not released to Accounting.Those documents are from previous period and also also those periods were already closed.
Now what should i do? if i want to release the invoice documents which are created in previous periods.Kindly advice me.
Thanks
Supriya

Hi Supriya,
Please open previous period for posting. Please follow the given below path:-
SPRO  Financial Accounting  Financial Accounting Global Settings  Document  Posting Periods  Open and Closed Posting Periods
Here you need to enter Posting Period Variant name assigned to company code and other detail like account number.
To know the Posting Period Variant follow this path:-
SPRO  Financial Accounting  Financial Accounting Global Settings  Document  Posting Periods  Assign Variants to Company Code
Or else you can take help of some FI guy.
Regards,
Anand

Self tuning threads are not releasing even though server running fine.

One of the cluster instance is running fine and serving the requests with good response but there self tuning threads are not releasing .I am not seeing any stuck threads in logs and no errors. why threads are not releasing.How we can troubleshoot this issue. May I know what are the cause of this.

Arun thanks for your quick response
Here is the threads details
Active Execute Threads 192
Execute Thread Total Count 222
ExecuteThreadIdleCount 190
QueueLength 0
PendingUserRequestCount 0
completed request count 36659285
HoggingThreadCount     1
StandbyThreadCount 30
Throughput 7.5
More number of threads are waiting for lock
Here is the sample thread dump.
"[ACTIVE] ExecuteThread: '218' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@faf757 WAITING
     java.lang.Object.wait(Native Method)
     java.lang.Object.wait(Object.java:474)
     weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:156)
     weblogic.work.ExecuteThread.run(ExecuteThread.java:177)
"[ACTIVE] ExecuteThread: '217' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@12c34ef WAITING
     java.lang.Object.wait(Native Method)
     java.lang.Object.wait(Object.java:474)
     weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:156)
some threads are blocked
ExecuteThread: '9' for queue: 'weblogic.socket.Muxer'" waiting for lock java.lang.String@1f39d37 BLOCKED
     weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:93)
     weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '8' for queue: 'weblogic.socket.Muxer'" waiting for lock java.lang.String@1f39d37 BLOCKED
     weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:93)
     weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
     weblogic.work.ExecuteThread.run(ExecuteThread.java:177)
"[STANDBY] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1bd18aa WAITING
     java.lang.Object.wait(Native Method)
     java.lang.Object.wait(Object.java:474)
     weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:156)
     weblogic.work.ExecuteThread.run(ExecuteThread.java:177)

Bill doc could not be released to accounting automatically

I have a problem on a particular billing type (document category P u2013 debit note) where the billing document could not be released to accounting automatically upon saving. The message VF050 is shown with Document xx saved (no accounting document generated). Subsequent release of the billing document to the accounting manually has no problem and no error was thrown. Looking through the account determination analysis shows that the correct revenue account is determined, so there should be no problem with the account determination setup. The billing type is also not set up with posting block, so it should release to accounting automatically.
What could be the possible problems or any other areas that I could check to trace the problem?
kt

Hi KT
First of all check in VOFA wheather Posting block has been maintained or not
Secondly also check wheather Revenue Account determination procedure has been done or not
Run VFX3 and finally pass it on to FI and while passing it on to FI you can check why the error has occurred
Regards
Srinath

Billing Document not released to Accounting -Issue

Hi,
While releasing the billing document,it is not releasing to accounting and giving the below error log.
Thanks
Supriya

Diagnosis
    When condition "ZSCM" (application "V") was transferred to the value field "VV139" in operating concern "AFCO" in Profitability Analysis, the following became apparent:
u2022     The condition can take both positive and negative   values
u2022     The flag "Transfer values with +/- signs" has not be set in Customizing for value field assignment.
    Inconsistencies in the data could occur as a consequence.
System Response
    It is not possible to post the document in Profitability Analysis.
Procedure
    Set the flag "Transfer values with +/- signs" for the condition "ZSCM".
    You should set the flag "Transfer values with +/- signs" selectively for individual conditions if:
1. The conditions can take both negative and positive values (for example, in the case of conditions that describe a transfer price surcharge or a loss deduction).
2. The conditions appear several times in a billing document and thus cause a debit posting as well as a
    credit posting (this is the case, for example, when creating or cancelling reserves).
By activating the flag "Transfer values with +/- signs", you balance the positive and negative values in a
condition. You can thereby guarantee that the sum of the negative and positive condition values is displayed as the correct total value in the value field assigned to the condition.
Caution when in the production system!
    If you have already used condition "ZSCM" to post data in the production system, then the sign in
    Profitability Analysis may differ from the previous sign as a result of the flag "Transfer values with +/-
    signs" having been activated. See the F1 Help documentation on the field "Transfer values with +/-
    signs" or the OSS note 52849. If deviating signs occur, it makes sense to move condition "ZSCM" to a new value field! Contact your system adviser or SAP.
    The +/- signs are handled as follows for the flag "Transfer values with +/- signs":
    Billing document (normal) "trans.with signs" "trans.w/o signs"
     Debit posting                   negative     positive       (such as sales deductions)
     Credit posting                  positive      positive       (such as revenues)
    Credit memos/returns    "trans.with signs" "trans.w/o signs"
     Debit posting                   negative     negative       (such as revenues)
     Credit posting                  positive       negative       (such as sales deductions)
    Maintain Condition Assignment to Value Fields u2013 SD Condition
    Maintain Condition Assignment to Value Fields u2013 MM condition
Procedure for System Administration
Thanks
Supriya

Natures of classes of accounts for posted document are not balanced

Hi
Can anyone help me with this error:
"Natures of classes of accounts for posted document are not balanced"
I am getting this error while doing GR(posting goods) using 561 movement type for a material.
While I am able to post Goods with another material having same valuation class and Profit Center.
Thanks
Neha

better post this question in procurement or (pure) finance forum!

Exchange rate diff. accts are not defined for account 16145110currency INR

Dear SAP Gurrus,
I am facing a problem while making payment against invoice, receiving payment against invoice, clearing advance payment and advance receipts through T-code F-53, F-28, F-44 and F-32. System is allowing me to select the invoices against which I want to do the clearing but when I go for simulation I am getting the following error -
' Exchange rate diff. accts are not defined for account 16145110currency INR'.
When I click on the error message the performance assistant gives methe following details:
Exchange rate diff.accts are not defined for account 16145110 currency INR
Message no. F5062
Diagnosis
The accounts for posting the exchange rate differences could not be determined. For the specified G/L account and the specified currency key, no corresponding exchange rate difference accounts were determined.
System Response
The system cannot generate the exchange rate difference posting.
Procedure
By pressing ENTER, you achieve that the document is reset to a status without automatic posting. In another window, you can complete the default settings for exchange rate differences and post the document afterwards.
Proceed
My client is local. Even the local currency is set to 'INR'. There is no foreign currency involced while making invoices, payment and receitps. Eventhough the system is giving me error. As a result I am not able to clear open items. Please give me some feasible solution so that I can clear the open items.
Thanks in advance
Regards
Shreyas Wani

hi,
As you said, you are not maintaining any Exchange rate differences, It may not be required a Exch rate Diffrences account.
Please check whether you have created any Group / Parrallel curencies etc in co.code level.
Please go through the notes 209580 / 89531, hope it helps you.
Regards
Kanna

Billing document are not flowing into FI and COPA

Hello SAP CO gurus,
please help me out by giving possible reasons why Billing document are not flowing into FI and COPA.
what are the settings need to check?
is there any option to get release by manual?
Initiatives rewards with points........
Regards
Chandra.

Hello Chandra,
Check whether any standard cost estimate is existing for that material for which your billing. If it is there then check whether costing key from COPA is able to access the cost estimate.
I am also working on the same issue but not solved yet.
regards
Nivas

Insufficient Authorization old Invoices Will Not Release to Accounting

I have some old invoices that will not release to accounting. Instead of trying to secure a new credit card from the customer how can I remove the credit card information/or trick the order into thinking it doesn't need it so that I can get the open billing documents to the customers open account?
Please any help will be appreciated.
Again the error message is insufficient authorization, need to get these documents released to accounting.

That is true...if it has been partially utilized in another Billing doc, then it wont let delete the lines...
So when this hapenned to me, this is what i did....and maybe this is not the best practice.
I first got a Manual authorization in the sales order. Now generally we get the auth. from a 3rd party application Delego. So when we did the manual auth, we just entered a fake Auth number. This way, we tricked the system to let us post the Invoice to accounts. But definitely it posted to the card receivable account insted of the customer account. Now the settlement of this item would fail because the Auth number is not valid but the settlement fails only after it does the additional G/l posting to post to the Clearing account. To clear off this clearing account posting, we created a credit memo for the same amount and again with a fake Auth so now when this credit is processed for settlement, it also fails but reverses the provious debit...so that all accounts are now all balanced out.
So now remains the customer....so we finally did a Debit memo equal to the original invocie amout and now this posts to the customers account.
I was unable to find any other solution and was skeptical of doing any enhancement or changes just for a single case. Pls also let me know if you come across any better ideas.

Backened documents are not getting updated in Classic Scenario

Hi,
We are using SRM 7.0 version and we are working on classic scenario where the shopping cart - RFX - Contract are created in SRM and the PO - GR - IR are created in ECC. The blackened documents which are created in ECC PO - GR and IR these documents are not getting updated in SRM system.
Is there any business functions to be activated.

Hi Sunil,
You manually run report ""BBP_GET_STATUS_2" after PO is created in MM. Then check if the follow-on-docs are updated in SC.
If it is working fine after you manully run report, you will have to properly set time to run this report automatically.
Best Regards,
Anu
Edited by: Anuradha UG on May 18, 2010 8:09 PM

Follow-on documents are not visible in MIRO in TEST server, awsys = PRD300.

Dear Experts ,
The Test Server was refreshed around mid-June 2011 with data of
Production Server. The follow-on documents are not visible for the
invoice documents in MIRO in TEST server due to value in tables
BKPF,RBKP : field : AWSYS = PRD300 .
The newly created Purchase Orders after the refresh, the accounting
documents can be seen for the Goods Receipt (MIGO_GR-display) and
Invoice documents (MIRO).
we had already raised this issue in March & got the feedback from SAP
as shown below.
accordingly we have developed & run the program "zzlogsys2" which
updates the Logsys/Awsys field from PRD300 ( of production server ) to
that of the current server i.e. TST300 as required.
after which the FI documents for the material documents are visible in
MIGO,but follow-on documents are not visible for the invoice documents
in MIRO.
we have Checked notes 781498 and 28958 to see if the logical system is
correctly assigned , where we found that in table RBKP after entering document number, Fiscal Year , the
Field AWSYS is "PRD300" & not "TST300" as it should be. We will take up the activity of updating table RBKP
also as we are currently doing for tables MKPF & BKPF.
But to have clear picture as to what we are doing is correct , pl
advise about the following :
1) Is it a correct process done by our SAP-Basis team , that every time
any Server ( e.g. Test or Quality ) is refreshed with Production server
data, the Field AWSYS in various transaction tables gets value as
"PRD300" which then is required to replaced by running program such as
ZZlogsys.
REPORT ZZLOGSYS.
TABLES: T000, MKPF.
DATA: NEW_SYS LIKE MKPF-AWSYS.
PARAMETER: OLD_SYS LIKE MKPF-AWSYS.
SELECT SINGLE * FROM T000 WHERE MANDT EQ SY-MANDT.
NEW_SYS = T000-LOGSYS.
CHECK NOT NEW_SYS IS INITIAL.
UPDATE MKPF SET AWSYS = NEW_SYS
WHERE AWSYS = OLD_SYS.
WRITE:/ 'Number of updates: ', SY-DBCNT.
2) if the above process is correct & normal , then which are the other
tables in a particular server ,apart from tables MKPF,BKPF,RBKP , which
needs to be updated the value of field "AWSYS" in the same way
replacing value "PRD300".
3) if the process in point no. 1 is not correct , then what is the
correct process that the Basis team can do while refreshing any target
server with production data so that target server retains its value in
Field AWSYS & not showing "PRD300".
With 3 servers TEST,DEV & Quality , recently refreshed with production
server to bring all servers in Sync for a HR patch application, we have
this situation now in all 3 servers .
Thanks in advance ,
Anil Shanbhag

It is appropriate to move this thread from ERP-MM to [Enterprise Resource Planning (ERP)|Enterprise Resource Planning (SAP ERP);
Edited by: Jeyakanthan A on Jul 7, 2011 4:56 PM

Why Documents are not releasing to Accounting Automatically?any reason?

Similar Messages

Maybe you are looking for