Document not updated in consolidation(urgent issue)

Hi all
actually we are posted one document in 2006 at the time its generated accounting document.but its not generated in consolidation document.now any option to generate the only consolidation document.
Thanks&Regards
Satish
09892421477

Hi Hari,
Thanks for your reply. I have checked in this transaction code also. The system is showing the message as "The document is already posted".
But it is not updated any tables except the document number is updated in table J_1IPART2.
Is there any other reasons for not updating the tables.
Regards
RS

Similar Messages

RMCVNEUF - document not updated

The business recently made a change to the Item Categories that update LIS/SIS. They want us to load all historical documents with this Item Category to our SIS structures and DW. There was a change made to RMCVNEUF to allow for us to search all billing documents where Item Category = NLC, allowing us to use the statistical updating program to load only the historical documents wanted.
As a test, I found on NLC document and run it thru RMCVNEUF. I have checked the Redetermine Update Group check box. I get a message back saying: Data from billing document 9000878658 was not updated
Message no. M2210
Diagnosis
Data from documents used as a basis is required for the processing of billing documents.
System Response
The data in the billing document 9000878658 will not be updated
System Response
Ensure that all sales orders and delivery notes are processed before the billing documents.
NLC item category is now configured in SPRO to be statistically relevant. Why would this not update using RMCVNEUF? Config was changed on 4/16/10 to allow for NLC to update. It seems any document created with this item category prior to that date will not be updated using RMCVNEUF? Any ideas? Not sure of a better/easier way to get only the documents we want to load to SIS and then DW.
Thank you
Theresa

Hi Cathy,
It is genrated profit center document also but its not updated in Consolidation (Profit center dimension). If u have idea about this please help me.
Thanks
K.Satish

FI Documents not posted in consolidation

Hi All,
We have a issue where once the FI documents are posted, the consolidation documents are not created. I have checked customizing settings and realtime update is checked. We also dont receive any error message for realtime update.
Also, when i run CXNR or CXNX to reconcile between general ledger and consolidation ledger, it shows there are reconciliation differences
Any help would be appreciated.

We had the same issue in our company as soon as we started fiscal year 2011. I logged a ticket with SAP and they directed me to table TRWCA. See Note 601700.
In your system TRWA may look like this:
400 ECCS 2010 X
400 ECCS 2999
400 ECCS 9999 X
Use SM30 to add a tick beside 2999, and the documents will start posting to ECCS again. Use CXNM to post the documents that were not posted to ECCS.
Hope this helps.

Goods movement document not updating

Hi Gurus,
I have created the order with component and external services did the goods issues and service acceptance but while checking in Menu bar of order>Extras>Document for order---->Goods movements no movement document is updared.Pls guide me why the movement document is not updating,I am sure about the goods issue and service acceptance because Actual cost is coming..
Thanks,
Kumar

Hi,
For better chances of response, better to post this in MM forum of R/3.
Thanks - Pawan

RMCVNEUF....billing document not updating

The business recently made a change to the Item Categories that update LIS/SIS. They want us to load all historical documents with this Item Category to our SIS structures and DW. There was a change made to RMCVNEUF to allow for us to search all billing documents where Item Category = NLC, allowing us to use the statistical updating program to load only the historical documents wanted.
As a test, I found on NLC document and run it thru RMCVNEUF. I have checked the Redetermine Update Group check box. I get a message back saying: Data from billing document 9000878658 was not updated
Message no. M2210
Diagnosis
Data from documents used as a basis is required for the processing of billing documents.
System Response
The data in the billing document 9000878658 will not be updated
System Response
Ensure that all sales orders and delivery notes are processed before the billing documents.
NLC item category is now configured in SPRO to be statistically relevant. Why would this not update using RMCVNEUF? Config was changed on 4/16/10 to allow for NLC to update. It seems any document created with this item category prior to that date will not be updated using RMCVNEUF? Any ideas? Not sure of a better/easier way to get only the documents we want to load to SIS and then DW.
Thank you
Theresa

Note 142349 says
Summary
Symptom
If in the statistical setup of the sales information system you select option 'Redetermine update group', the following error messages may occur:M2206, M2207, M2208, M2209, M2210, M2211.
The documents specified in the messages may be displayed correctly during an update simulation.
Additional key words
OLI8, OLI9, RMCVNEUL, RMCVNEUF
Cause and prerequisites
During the redetermination of the update group in the reorganization, information from preceding documents is written to the intermediate tables MCVSRFK (document header) and MCVSRFP (document item), which are relevant for the determination of the update group of the subsequent documents.
Solution
To fill these intermediate tables, the reorganization of sales orders must be performed before the reorganization of deliveries or the reorganization of sales orders and deliveries must be performed before the reorganization of billing documents (in each case with option 'Redetermine update group'.
Note
After the successful reorganization the above-mentioned help tables should be deleted with report RMCVNEDE to avoid uneccessary data collection and the increasing loss in performance during the following reorganization runs.
thanks
G. Lakshmipathi

Accounting Document not updated in BKPF for JV by J1IH

Hi
The user posted JV through transaction code J1IH.
The document number is updated in table J_1IPART2 but when the user is trying to see the same document in FB03 we are getting the error message as "the document is not exist or not archived".
And we have checked in tables BKPF and BSEG we did not find this document.
Can anyone please suggest how to find the reason why the system is not updated this document?
Regards
RS

Hi Hari,
Thanks for your reply. I have checked in this transaction code also. The system is showing the message as "The document is already posted".
But it is not updated any tables except the document number is updated in table J_1IPART2.
Is there any other reasons for not updating the tables.
Regards
RS

Material document not updated in inspection lot QALS table

HI
The inspection lot created for 04 inspection type during Goods Receipt.
The material document is appearing in the inspection lot but found not updated in table entries. i.e.., QALS -MBLNR
When i checked other inspection lots it was found updated. How this happened ?
Any Snote to be applied?
Thanks

Hi,
Check the number ranges for material documents. (with year) for document type WE in OMBT transaction code.
If same material document number repeats in the same calendar year,then document update will be terminated.
As, document no. will be already existing in tables, system won't allow to update the same no. again.
Thanks & Regards,
Anand.

Accounting Document not updated after Vf01(billing)

Hi Gurus,
After creating invoice in vf01 when i m looking at accounting document, then my value is updated but the quantity is not updated in fb02.
when i see table BSEG then the value of MENGE is not updated there.
It is always coming ZERO.
Thanks in advance

Hi
Please check whether FI doculments summarisation is active for this field under procedure VBRK.
Regards

Controlling segment of FI document not updated through FIDCCP02

hello..
We are using FIDCCP02 basic type for posting FI document from a third party system via XI.
IDOC gets succesfully posted and generates FI document as well (visible in FB03)..it is also showing cost center details in the FI line item as per requirement..
BUT the problem is, while posting the document thru IDOC..<b>it is not updating the controlling document for that Cost Center</b>...though it gets updated when we manually create the FI document.
we checked out the note 114814 , it says that FIDCCP02 does not update controlling component...so use some other IDOC type !!!
now the question is...which basic type / Function module should we use for posting CO details for the FI document ??? and moreover how to incorporate this functionality with the process code i have already developed ( working absolutely fine as far as FI document is concerned )..
please reply to this as soon as possible..
regards
nidhi

<b>Cost Center Accounting</b>
In this activity, you make settings required for distribution in Cost Center Accounting.
There is a difference between settings for distribution method one (centralized Cost Center Accounting), and those for method two (decentralized Cost Center Accounting).
Consistency Check
The function in this section carries out a consistency check of the settings made here. We recommend you use this consistency check to make the relevant settings.
Execute the function in the decentralized systems. Then you can check whether the settings between the systems for the required message types have been correctly maintained.
Double-click on a line in the consistency check log to make the required settings.
You must have maintained the partner profiles in all the systems.
Notes on Overhead Cost Controlling
You make Overhead Cost Controlling settings in Customizing, under Controlling.
The following settings are required to distribute a controlling area:
The distribution method must be defined in the controlling area for the basic data in the "Distribution method" field. You can choose between distribution method one or two.
The logical system name of the central controlling system must be defined in the controlling area for the basic data in the "Logical system" field. The logical system name is defined in the installation and in the client settings. (In IMG under:
Basis Components
Distribution (ALE)
   Sending and Receiving Systems
      Logical Systems
        Assign Logical System to a Client
If you use distribution method two, you also assign all cost centers to a master system, which is the logical system for the cost center.
If you want to use the profit center accounting, read section Distribution scenarios -> Profit Center Accounting
If you want to use profitablitity analysis, read section Distribution scenarios -> Profitablitity Analysis.
Synchronization of settings using the transport system
Some settings for overhead cost controlling need to be in all systems in the same form.
The easiest way to ensure this, is by doing your customizing in a centralized system, and then distributing the data to all systems affected.
The transport system is normally used for the first time that decentralized controlling is provided with customizing data.
For information on compiling the transport orders for decentralized controlling systems, see the Implementation Guide (IMG), under the section on Controlling -> General Controlling -> Productive Start Preparation -> Transport System Settings.
Individual setting synchronization
If you do not make the settings for overhead cost controlling centrally in a Customizing system, but individually in each of the affected systems, then ensure that they all contain the following data in the same form:
Data for all controlling areas:
Currencies
Charts of accounts
Attributes for the controlling area: Basic data
Distribution method
Logical system
Currency type
Currency
Chart of accounts
Fiscal year variant
Standard hierarchy for cost centers
Activated reconciliation ledger indicator
Attributes of the controlling area: Control indicators
Cost Center Accounting activated
Indicator for all currencies
Indicator for company code validation
Assignment of controlling area - company code
Assignmeents between controlling areas and company codes can only be maintained centrally and distributed, if the assignments between local and global company codes match.
Otherwise, you need to make the assignments individually in each system.
The concept of global company codes is explained in Customizing, under the following path:
Predefined ALE Business Processes
    Accounting
      Financial Accounting
Notes on Distributing Plan Prices
Plan prices for the cost center/activity type combination are distributed using the "COACTV" message category. Before you do this, you need to activate the integration for each planning version used and fiscal year.
To do this in the menu Cost Center Accounting,
choose Planning -> Planning aids -> Integration active in
For distribution method one, you need to activate the integration in the centralized system. For method two, you need activate integration in both the centralized and the decentralized systems.
Notes on Distributing the Reconciliation Ledger
When Cost Center Accounting is distributed, you also need to distribute the reconciliation ledger.
If centralized Cost Center Accounting is used in a system other than the centralized general ledger, then you also need to make some more settings in Customizing in addition to the setting for the message flow between decentralized and centralized cost accounting. This is for the distribution of the reconciliation ledger.
The "RCLROL" message dispatch (from decentralized and centralized Cost Center Accounting to the centralized general ledger) must also be inserted in your distribution model with the company code filter object.
You need to maintain these two message flows in the communication parameters.
There is a restriction, whereby reconciliation postings can only be made on company code level.
Distribution Method One: Partner profiles
Partner profiles in the centralized cost accounting system
In the centralized cost accounting system, you need to maintain outbound partner profiles for each decentralized cost accounting system.
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
(RCLROL Roll-up reconciliation ledger
if the centralized system
for the controlling area and
the company code are different)
You need to maintain the inbound partner profiles for the each decentralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different)
Partner profiles in the decentralized cost accounting system
In each decentralized cost accounting system, you need to maintain outbound partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
CODCMT CO-Beleg
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-Up reconciliation ledger
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different).
You need to maintain inbound partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
(RCLROL Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).
Note
The COSCOR (cost centers (core)) and COACOR (activity types (core) message types are obsolete, and should not be used any more. Under no circumstances should they be used with the ZH>COSMAS (cost centers) and COAMAS (activity types) message types.
Distribution Method Two: Partner profiles
Partner profiles in the centralized cost accounting system
You need to maintain outbound partner profiles for each decentralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
CODCMT CO document
(RCLROL Roll-up reconciliation ledger
if the centralized system for
the controlling area and
the company code are different).
You need to maintain the inbound partner profiles for each decentralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
COTOTL Totals records
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system of
the company code,
if the centralized system for
the controlling area and
the company code are different).
Partner profiles in the decentralized cost accounting system
In each decentralized cost accounting system, you need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
COTOTL Totals records
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system for
the company code,
if the centralized system for
the controlling area and
the company code are different).
You need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
CODCMT CO document
(RCLROL Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).
Note
The COSCOR (cost centers (core)) and COACOR (activity types (core)) message types are obsolete and should no longer be used. Under no circumstances should they be used with the COSMAS (cost centers) and COAMAS (activity types) message types.
Error handling
Specifying responsibilities for workflow error processing in the distribution environment.
Workflows are created to problems in cost accounting in the distribution environment. You need to specify employees who are responsible for the errors. You can use ALE-customizing for maintenance:
Basis Components
Distribution (ALE)
    Error Handling
Distribution Method One:
Specifying responsibility in the centralized cost accounting system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSFET_Error COSFET Inbound error
COAFET_Error COAFET Inbound error
CODCMT_Error CODCMT Inbound error
RCLROL_Error RCLROL Inbound error
Specifying responsibility in the decentralized system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSMAS_Error COSMAS Inbound error
COELEM_Error COELEM Inbound error
COAMAS_Error COAMAS Inbound error
COGRP1_Error COGRP1 Inbound error
COGRP2_Error COGRP2 Inbound error
COGRP5_Error COGRP5 Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
Distribution Method Two:
Specifying responsibility in the centralized cost accounting system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSFET_Error COSFET Inbound error
COAFET_Error COAFET Inbound error
COTOTL_error COTOTL Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
CODCMT_Error CODCMT Inbound error
RCLROL_Error RCLROL Inbound error
Specifying responsibility in the decentralized system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSMAS_Error COSMAS Inbound error
COELEM_Error COELEM Inbound error
COAMAS_Error COAMAS Inbound error
COGRP1_Error COGRP1 Inbound error
COGRP2_Error COGRP1 Inbound error
COGRP5_Error COGRP1 Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
CODCMT_Error CODCMT Inbound error
Note
In the distribution model, you must maintain a company code or a controlling area as a filter object for the "RCLROL" message type.
Check consistency
After you have made the settings for distributed Cost Center Accounting, you can check the settings for consistency (see Set up Communication , Partner Profiles, and Check Model Settings).
Cost Center Accounting
In this activity, you make settings required for distribution in Cost Center Accounting.
There is a difference between settings for distribution method one (centralized Cost Center Accounting), and those for method two (decentralized Cost Center Accounting).
Consistency Check
The function in this section carries out a consistency check of the settings made here. We recommend you use this consistency check to make the relevant settings.
Execute the function in the decentralized systems. Then you can check whether the settings between the systems for the required message types have been correctly maintained.
Double-click on a line in the consistency check log to make the required settings.
You must have maintained the partner profiles in all the systems.
Notes on Overhead Cost Controlling
You make Overhead Cost Controlling settings in Customizing, under Controlling.
The following settings are required to distribute a controlling area:
The distribution method must be defined in the controlling area for the basic data in the "Distribution method" field. You can choose between distribution method one or two.
The logical system name of the central controlling system must be defined in the controlling area for the basic data in the "Logical system" field. The logical system name is defined in the installation and in the client settings. (In IMG under:
Basis Components
Distribution (ALE)
   Sending and Receiving Systems
      Logical Systems
        Assign Logical System to a Client
If you use distribution method two, you also assign all cost centers to a master system, which is the logical system for the cost center.
If you want to use the profit center accounting, read section Distribution scenarios -> Profit Center Accounting
If you want to use profitablitity analysis, read section Distribution scenarios -> Profitablitity Analysis.
Synchronization of settings using the transport system
Some settings for overhead cost controlling need to be in all systems in the same form.
The easiest way to ensure this, is by doing your customizing in a centralized system, and then distributing the data to all systems affected.
The transport system is normally used for the first time that decentralized controlling is provided with customizing data.
For information on compiling the transport orders for decentralized controlling systems, see the Implementation Guide (IMG), under the section on Controlling -> General Controlling -> Productive Start Preparation -> Transport System Settings.
Individual setting synchronization
If you do not make the settings for overhead cost controlling centrally in a Customizing system, but individually in each of the affected systems, then ensure that they all contain the following data in the same form:
Data for all controlling areas:
Currencies
Charts of accounts
Attributes for the controlling area: Basic data
Distribution method
Logical system
Currency type
Currency
Chart of accounts
Fiscal year variant
Standard hierarchy for cost centers
Activated reconciliation ledger indicator
Attributes of the controlling area: Control indicators
Cost Center Accounting activated
Indicator for all currencies
Indicator for company code validation
Assignment of controlling area - company code
Assignmeents between controlling areas and company codes can only be maintained centrally and distributed, if the assignments between local and global company codes match.
Otherwise, you need to make the assignments individually in each system.
The concept of global company codes is explained in Customizing, under the following path:
Predefined ALE Business Processes
    Accounting
      Financial Accounting
Notes on Distributing Plan Prices
Plan prices for the cost center/activity type combination are distributed using the "COACTV" message category. Before you do this, you need to activate the integration for each planning version used and fiscal year.
To do this in the menu Cost Center Accounting,
choose Planning -> Planning aids -> Integration active in
For distribution method one, you need to activate the integration in the centralized system. For method two, you need activate integration in both the centralized and the decentralized systems.
Notes on Distributing the Reconciliation Ledger
When Cost Center Accounting is distributed, you also need to distribute the reconciliation ledger.
If centralized Cost Center Accounting is used in a system other than the centralized general ledger, then you also need to make some more settings in Customizing in addition to the setting for the message flow between decentralized and centralized cost accounting. This is for the distribution of the reconciliation ledger.
The "RCLROL" message dispatch (from decentralized and centralized Cost Center Accounting to the centralized general ledger) must also be inserted in your distribution model with the company code filter object.
You need to maintain these two message flows in the communication parameters.
There is a restriction, whereby reconciliation postings can only be made on company code level.
Distribution Method One: Partner profiles
Partner profiles in the centralized cost accounting system
In the centralized cost accounting system, you need to maintain outbound partner profiles for each decentralized cost accounting system.
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
(RCLROL Roll-up reconciliation ledger
if the centralized system
for the controlling area and
the company code are different)
You need to maintain the inbound partner profiles for the each decentralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different)
Partner profiles in the decentralized cost accounting system
In each decentralized cost accounting system, you need to maintain outbound partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
CODCMT CO-Beleg
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-Up reconciliation ledger
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different).
You need to maintain inbound partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
(RCLROL Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).
Note
The COSCOR (cost centers (core)) and COACOR (activity types (core) message types are obsolete, and should not be used any more. Under no circumstances should they be used with the ZH>COSMAS (cost centers) and COAMAS (activity types) message types.
Distribution Method Two: Partner profiles
Partner profiles in the centralized cost accounting system
You need to maintain outbound partner profiles for each decentralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
CODCMT CO document
(RCLROL Roll-up reconciliation ledger
if the centralized system for
the controlling area and
the company code are different).
You need to maintain the inbound partner profiles for each decentralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
COTOTL Totals records
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system of
the company code,
if the centralized system for
the controlling area and
the company code are different).
Partner profiles in the decentralized cost accounting system
In each decentralized cost accounting system, you need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
COTOTL Totals records
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system for
the company code,
if the centralized system for
the controlling area and
the company code are different).
You need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
CODCMT CO document
(RCLROL Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).
Note
The COSCOR (cost centers (core)) and COACOR (activity types (core)) message types are obsolete and should no longer be used. Under no circumstances should they be used with the COSMAS (cost centers) and COAMAS (activity types) message types.
Error handling
Specifying responsibilities for workflow error processing in the distribution environment.
Workflows are created to problems in cost accounting in the distribution environment. You need to specify employees who are responsible for the errors. You can use ALE-customizing for maintenance:
Basis Components
Distribution (ALE)
    Error Handling
Distribution Method One:
Specifying responsibility in the centralized cost accounting system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSFET_Error COSFET Inbound error
COAFET_Error COAFET Inbound error
CODCMT_Error CODCMT Inbound error
RCLROL_Error RCLROL Inbound error
Specifying responsibility in the decentralized system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSMAS_Error COSMAS Inbound error
COELEM_Error COELEM Inbound error
COAMAS_Error COAMAS Inbound error
COGRP1_Error COGRP1 Inbound error
COGRP2_Error COGRP2 Inbound error
COGRP5_Error COGRP5 Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
Distribution Method Two:
Specifying responsibility in the centralized cost accounting system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSFET_Error COSFET Inbound error
COAFET_Error COAFET Inbound error
COTOTL_error COTOTL Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
CODCMT_Error CODCMT Inbound error
RCLROL_Error RCLROL Inbound error
Specifying responsibility in the decentralized system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSMAS_Error COSMAS Inbound error
COELEM_Error COELEM Inbound error
COAMAS_Error COAMAS Inbound error
COGRP1_Error COGRP1 Inbound error
COGRP2_Error COGRP1 Inbound error
COGRP5_Error COGRP1 Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
CODCMT_Error CODCMT Inbound error
Note
In the distribution model, you must maintain a company code or a controlling area as a filter object for the "RCLROL" message type.
Check consistency
After you have made the settings for distributed Cost Center Accounting, you can check the settings for consistency (see Set up Communication , Partner Profiles, and Check Model Settings).
reward points if it is usefull ....
Girish

Cash desk and payment lots documents not updating in DFKKOP table

Dear Experts,
I have noticed that my cash desk payments and payment lot documents are not getting updating in the DFKKOP table. I have identified that for this documents, the document class is updated with "1" which means "Document does not have FI-CA items".
But, the postings where shown in the FPL9 transactions and clearing is happening as per the settings and requirements.
So please update me, on what basis the system would determine the document class for the document types in contract accounting..
Your inputs on this issue will be really helpful for me.
Thanks
Aditya Viswanath

Hi Aditya,
In a simple word, whichever documents are posted with MAIN/SUB creates a new row in DFKKOP with document number in DFKKOP-OPBEL.
If a payment is posted as an open credit item, it should be there DFKKOP-OPBEL field and BETRW and BETRH will be populated with payment amount.
However if a payment is posted as a clearing document against a debt, system updates that row of DFKKOP where DFKKOP-OPBEL is the cleared document number (debt, mostly an invoice). Clearing document (DFKKOP-AUGBL) of that row is updated with the payment document number.
In either of the cases DFKKKO and DFKKOPK are updated and below are the reason.
DFKKKO - document header level information (as who created, at what time, origin key, reco key etc.)
DFKKOPK - (GL level information of the document)
For payment lot and payment document related information you can refer DFKKZK, DFKKZP and DFKKZPT tables.
Hope it clarifies your query.
Thanks, Bodhisattwa

Accounting Document not generated after Post goods issue in delivery order.

Dear Experts
Greeting of the daays,
Need your help on below issue.
After making the post goods issue ,the system is not making the accounting document.
The error given by the system is as follows:
Material document 12365 does not include an accounting document
Diagnosis
The system cannot find an accounting document for the material document 12365.
Possible reasons for this are:
The goods movement has no relevance to accounting. Therefore, the system did not generate an accounting document for the material document.
The material document is a document that was posted before Release 2.1. Such documents must be converted so that the system can find the relevant accounting document.
The procedure for the subsequent calculation of value is not active in your system. For further information, refer to the documentation on the program for valuating goods movements: RM07MWBU.
__Solution what I tried to solve this issue ,but not successful.__
__Solution 1- maintain OMS2__
__Solution 2 - maintain OMJJ- movement type 601 - PRCTR is required entry.__
__Solution 3 - price maintain is material master.__
__Solution 4 - OBYC - BSX - 7920 - GLA/c and GBB- VAX and VAY - 7920 GLA/c.__
__Pls let me know if there is any confirgation is missing.__

Hi
Do this checks:
In tcode OBYC check if you have the proper entries.
Go to tcode OKB9 and do the settings for the G/L acc. that you have in OBYC.
To populate PRCTR you can use OKB9 and you can check if you have values in MARC-PRCTR.
I hope this helps you
Regards
Eduardo

COPA document not generated when Post Goods Issue is reversed.

Hello Friends,
WE uses Stock Transport Order in two steps for transfering Stock from one plant to another. We have defined a Condition type FRB1 to capture the Freight cost involved in the stock transfer.
When the Post goods issue is done for the Stock Transport Order. following Accounting documents are generated.
Accounting
Profit Center
COPA
Spec. Purpose Ledger
Controlling Document
Material Ledger document.
But When the Post goods issue is reversed through transaction code VL09 all the above documents are generated except for COPA document. Though in controlling document it shows the object type hit is REO i.e profitability Analysis
For further information we have mapped cost element (600150) with Value field in PA transfer structure (Direct assignment from FI and MM. Movement type used for PGI are 641 & 642.
Thank you

Dear Colleagues
I thank all those who put in thier time and efforts for possible solution for my problem. But I could resolve this issue with help from SAP.
Basically in costing based COPA the system does not post the cost of goods sold to COPA during goods issue but it is done at the time of posting the invoice since the system wants to see the revenues and the COGS values together.
Since the system posts the COGS into COPA at the time of invoice posting, you will appreciate that if this is also done during goods
issue then you will have duplicate entries in your COPA (i.e. the COGS will be doubled).
If in transaction VL01N/VL02N a costing-based line item would be posted, the costs would be double in CO-PA (the billing and goods issue). For this reason, no costing based line items will be created in the standard R/3 system for transaction VL01N/VL02N.
If for some reason you still wish to post the COGS to COPA during goods issue you have to do the same thro a modification of the system.In your case you have applied note 214381 for the same. Please note here that movement type '641' is used as an example. For other movement types you will need to code accordingly.
as per note 337488 point 2. the changes of note 214381 were not required in our case. Therefore we reverted these changes in LKEIIF01 and added the relevant coding for movement type 642 in function COPA_DOCUMENT_CHECK as per note 337488 point 2.
Looking forward for your continued support
Regards
Umesh Gothankar

Financial Document not updated with Sale Order Number

Hello,
I wish to update the Financial document posting from the billing document with the Sales order and line item number against the revenue account.
This is not populating in COBL-KDAUF.
I have seen some other messages concerning this, but none with answers.
Is this possible, I assume it is.
If so, are there any other necessary settings?
We are not using CO-PA, and I can get the reference number & /or allocation field to populate with the sales order number but not line item. But I want the coding block filled so that BSEG VBEL2 is populated.

Hi Roger,
In the situation that you have a 1:1 relation this is possible with a substitution and look then to the order in the first line from the invoice.
Where you can have a look to is the sumarization in FI and CO. TC OBCY for VBAK and VBRK.
Example:
When you have 2000 posting lines in an invoice the system can create 1 posting line by used G/L account
With this transaction you can set-up that there is create one posting line by:
(G/L account)
Sales order number
You have first to look how your set up is. (perhaps when this is set-up correct you have already the order number in the field).
Paul

Material document not updated in Table MSEG,MKPF

Hi,
when i post the GR, Materail doument is posted and matereail doument number is shown, but when i go to Display mode of the materail docuemnt number. the message is coming" document numberXXXXX does not exist in calender year 2010" Message no: M7062.
if i see the tables MKPF,MSEG,EKBE there is no entry dispalyed..
due to this problem my work is pending in all Procure to pay scenario..
can you provide the solution..
regards,
Obulesu

Hi,
Check the number ranges for material documents. (with year) for document type WE in OMBT transaction code.
If same material document number repeats in the same calendar year,then document update will be terminated.
As, document no. will be already existing in tables, system won't allow to update the same no. again.
Thanks & Regards,
Anand.

Pivot not updating - Still on July issue.

Hello, My TP was activated on 8th September and updated to WebOS v3.02 soon afterwards. It’s still showing the July issue of Pivot. There are no issues with WiFi connection, I can browse the App Catalog (v5.0.1600) and have downloaded several apps, even used WebOSDoctor yesterday to restore the original settings. It had preware installed which I’ve removed, a second TP used by the wife is also showing the July issue. This unit has not had any third party OS modifications, it’s on the latest WebOS. Both TPs are UK stock from different vendors although I bought them second hand (sealed new). Any thoughts on how to update Pivot manually? Thanks.
Post relates to: HP TouchPad (WiFi)

Hi,
You can first update to the new table. Confirm data in new table is correct and then activate the request.
Please check your start routine and/or other routines in the transformation/update rule. Better you can do a simulate update.
Regards,
Frank

Document not updated in consolidation(urgent issue)

Similar Messages

Maybe you are looking for