Distributed check reconciliation (HR//FI)

All,
We are implementing HR in a seperate system ECC6.0 and keeping everything else (FI/CO/SD/MM) in 4.7. As per our current design, we will post payroll in the 6.0 environment and ALE (idoc) the payroll to 4.7.
What about check reconciliation? We will create our HR checks in 6.0 but the actual financial postings are needed in FI 4.7
What is the standard process for check reconciliation in distributed environments? How do we get the FI documents posted in 4.7 as the checks are getting cashed/cleared?
Do we copy tables (eg., PAYR)
Do we use Idoc functionality.
Please advise with as much detail possible.
Thanks,
Kuldeep

Hello,
Take a look at note 1137655.
Regards,
Carlos.

Similar Messages

Outgoing check reconciliation in FICA

Hi Folks,
For issuing customer refunds, we are generating checks in FICA using FPY1 payment program. We activated the event 940 which allows outgoing payment documents to be transferred to GL individually without summarization.
In FI-AP, vendor payments are handled using payment program F110. When the electronic bank statement is loaded in FI, how can we reconcile the data for checks on the FICA side. We tried to manually clear the FICA related checks on the FI side, but it was not updating the check status in FICA.
How can we update the status of checks encashed in the FICA side once EBS is uploaded?
Thanks,
Santosh

Hi
I think this is a difficult one. I guess if you could not tell the bank to seperate the amounts by check lots, then you should somehow find a way of summing up the daily lots so that the bank reconciliation system to work with the daily check lot totals for easy matching with bank single credit entry.
You might need to talk with your developers to write a proigram to sumup the daily lot for the purpose of the recociliation system.
Thanks.
regards,
David

Reconciliation Rules in OIM 9.1

Hi,
I need your input in the below mentioned problem.Lets assume we call the field UserLogin in OIM and UserID in Target System ( Target Systems are Exchange and Active Directory).
A Sample UserLogin is A123456 and a sample UserID is 8123456 Both of these are fields are 7 characters long.
In the Reconciliation rule, we can compare last 6 characters of both UserLogin (OIM) and UserID (AD) by using endswith function and transforming by using substring function in Recon Rules of the Design Console, but the difficulty is with second part of the rule is, If the above condition evaluates to true,we want to add one more recon rule, which should check whether UserLogin (OIM) field in starts with number say 8.
can you please let us know, how and what is the efficient/best way of writing this recon rule.
Thanks for your help in Advance
Regards

http://download.oracle.com/docs/cd/E21764_01/doc.1111/e14309/resmgt.htm#CHDDJCAH
Check : Reconciliation Fields Tab section

FI- Reconciliation ledger

Hi,
I would like to know what is meant by Reconciliation Ledger and How we can create Reconciliation Ledger in the SAP - Retail

Hi Ravi,
You can use reconciliation postings to transfer cross-company code; cross-business area or cross-functional area postings made in CO that are relevant to FI, and to automatically create reconciliation postings there. You can make these reconciliation ledger postings at any time
In the information system, you can compare the account balances between CO and FI for a particular period using reconciliation reports. In these reports, the system displays a difference for a reconciliation posting made outside of the period. The cost flow overview report is more suitable for checking reconciliation between CO and FI. To ensure that all reconciliation postings are transferred, you should only execute reconciliation at period-end, after closing all CO postings. If you execute reconciliation more than once, the SAP R/3 System only updates difference values since the last reconciliation run.
You can give me your personal Id, I can send you the documentation on step by step to be done in Reconciliation ledger.
Regards
Sridhar

View reconciliation history error

Can anybody hint what this error mean, when I selected AD resource and checking reconciliation history.
An unrecoverable error has occurred processing the request. Contact your system administrator.
Syslog ID = LG-1111-111111.
Thanks for your help.

Application server restart did not do any good.
lh syslog gave me this output...a few last lines below
...assloader
2008-02-26 10:34:55.856 SV-0226-163455 E morx67pp SV ERROR Error starting thre
ad: Not enough storage is available to process this command.
2008-02-26 10:34:43.647 LG-0226-163443 F morx67pp LG ERROR could not create cl
assloader
2008-02-26 09:30:32.336 LG-0226-153032 F morx67pp LG ERROR could not create cl
assloader
but, when I go ../debug/Show_Memory.jsp, I see good enough space alloted.
However I also observed that sometime when I check for view reconciliation history I also ran into..
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.

FI Reconciliation SAPF180A

dear friends ,
My requirement was to work with Reconciliation with balance sheet adjustment in FI . if i run this program SAPF180A it will full fill .
Can any one help me how to work with thais program .
Regards
Reddy

Hi Ravi,
You can use reconciliation postings to transfer cross-company code; cross-business area or cross-functional area postings made in CO that are relevant to FI, and to automatically create reconciliation postings there. You can make these reconciliation ledger postings at any time
In the information system, you can compare the account balances between CO and FI for a particular period using reconciliation reports. In these reports, the system displays a difference for a reconciliation posting made outside of the period. The cost flow overview report is more suitable for checking reconciliation between CO and FI. To ensure that all reconciliation postings are transferred, you should only execute reconciliation at period-end, after closing all CO postings. If you execute reconciliation more than once, the SAP R/3 System only updates difference values since the last reconciliation run.
You can give me your personal Id, I can send you the documentation on step by step to be done in Reconciliation ledger.
Regards
Sridhar

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

Users reconciled into Oracle Identity Manager 9.1.0.2

Hello friends,
I have configured the process of reconciliation between Oracle Identity Manager and LDAP directory (Microsoft Active Directory), my question is: How I can find users who were reconciled to Oracle Identity Manager 9.1.0.2 and I have currently in Oracle through this process.
thank you very much

Hi,
in design console check : Reconciliation Manager -> query for reconciliation event for resource AD.
hope this helps.

Few users getting reconciled after running trusted recon

Hi Experts,
i ran a trusted recon for a particular Active Directory search base and it reconciled only 6 out of some 50 odd users. I checked if the remaininig users are already present in OIM, which they are not. I checked all the parameters and they look fine. Please kindly guide me on some pressure points to check for errors.
Thank you for your time.

Verify data of your users. Check reconciliation events, if they generated for all users. That would give you some idea. Click on re-evaluate button there to relink that specific user. Also make sure xlReconbatchsize system property is set to 500(by default). Also make sure (if this is cusomt code), bulk execute method of your schedule task is implemented properly.
If nothing is clear, put logs here.
regards,
GP

Standalone scenario of self-service procurement

Hi all,
I'm testing SRM5.0 right now. I'm new about SRM.
In the standalone scenario of the self-service procuremnt, only accounting data goes to R/3. Does anyone know how to verify the accounting data on R/3 through EBP? In other words, which tracsaction code of R/3 can I see the accounting data transferred automatically after I created the invoice on EBP?
Thanks a lot for your help.
Yuko

Hello Yuko,
invoices are sent to R/3 via IDOC BBPIV (transfers invoicing information to the back end in FI).
Checklist:
- check LS and backend definition
- check distribution model in SRM
- check distribution model in R/3 (created manually or distributed)
- check generated partner profiles in SRM
- check generated partner profiles in R/3
- check outbound IDOCs in SRM
- check inbound IDOCs in R/3
With transaction BD87, you can reprocess erroneous IDOCs, if for example the posting period is not opend in FI.
Rgds
Christophe

Google mail help

Someone would help me on this one? i have an hosted domain with google. Imap activated. Pop is not. setup within BIS is ok. receive my emails quickly. Gmail plugin installed as well. deletion from device to server is OK. but deletion from webmail to device won't happen. I've checked reconciliation: it's on.

jupit3r wrote:
and i don't find any support on blackberry website exceot those link sending to local dealers.
1. This BlackBerry Support Community Forum... you're here now.
2. The BlackBerry Techincal Solution Center, the big button above.
http://supportforums.blackberry.com/rim/i/nav_on/BBsupportForums_navOn_17.jpg
3. BlackBerry Answers, again, big button above, or
http://na.blackberry.com/eng/support/answers/
4. BlackBerry Incident Based Support
http://na.blackberry.com/eng/support/programs/technical/incident.jsp
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Wake On-LAN Operations

Hi everyone,
I have a little big problem with a ZW bundle.
Let me introduce what I want to do:
My target is to schedule the AntiVirus scan by night using a ZenWorks task, It will be very nice if the bundle sends Wake On-LAN command before execute the operations.
At the moment I create a "file bundle" and i specify a custom script (.bat) that execute the AV scan, write a log, and then TurnOff the machine.
When I schedule the distribution task i flag the Wake On-LAN check box, and the "Install after distribute" check box.
the result is this:
-Wake On-LAN works fine
-the distribution is in "pending" status
-installation doesn't start
If I force the Installation on the target machine, it starts and finish with the shutdown command.
When the next scheduled execution occour the result is:
-Wake On-LAN works fine
-distribution.. ??
-Installation doesn't start
have you any suggestions for me?
thanks
LB

lucabaxi,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Distributed HR/PY and Check Clearing

Hi experts -
Changing our landscape from a single integrated system to a distributed HR/PY and FICO environment (I.e. 2 different instances). In the distributed architecture I understand the Payroll Check (tcode RFFOUS_C) print program still runs in the HR/PY instance and the check register is also updated in the HR/PY instance. However, the GL posting that include open item managed bank clearing account(s) for payroll checks is updated only in the FICO instance (via ALE) by the Posting to accounting process.
Can anyone tell me how and where the EBS should be run to clear the payroll checks and the GL payroll check clearing open item account? Again, the payroll checks will be in the check register in the HR/PY system but the GL payroll check clearing open item account will be in FICO instance.
Anyone out there have experience with this scenario?
Thanks!

Have you worked specifically with a distributed HR/PY and FICO architecture? Or, are you answering this question based on your understanding of the payment process from FI? If you have not worked hands-on with the distributed HR/PY and FICO architecture I do not think you understand the issue.
In the distributed HR/PY architecture the payroll checks are created in the HR/PY instance. The creation of the GL entry for the payroll check bank clearing account is created by an entirely separate process - the PY GL Posting run and the distributed model posts the GL to the FICO instance. Therefore, the check register is in the HR/PY instance and GL payroll check bank clearing account in in FICO.

Distribut Open Item Acct and Reconciliation Acct in New GL

Hello,
We are using the New GL on ECC6.0. And I found it is impossible to distribute the open item management account and reconciliation account in New GL, instead, I was told to run assessement. By running assessmenent, I need to create a lot of new assessment account,which is every troublesome.
Does anyone have the work around solution?
Rachel

Hi again Milind Sonalkar,
the note you specified (1309427) tells :-
"Solution
Use the log (transaction SLG1, object FAGL, subobject OPENITEM) to find the clearings specific to ledger groups. Use these documents as templates to manually make the return postings using transaction FBB1. If you require help with regard to the manual return posting, contact SAP Support and refer to this note."
with this I understand that for the account, the program(trns FAGL_ACTIVATE_OP) executed is not able to post to rest of ledgers except the leading ledger and need to post by manually in FBB1? what is return postings in the note?
for more information for the account used is a balance sheet account and has open items after execution of old program "Z"RFSEPA02. so while trying to clear them by F-03 it sends the above(in 1st port) mentioned error. Here I understand that first need to post(clear) manually to those open items which are posted before marking OI. am I right?, please enlighten me.

Initial Bank Reconciliation Implementation - Outstanding checks

During the very first bank reconciliation the begining balance that the system enters as the beginning balance is $0. But of course in reality we have checks that have been written, but the suppliers have not cashed them prior to "go live" (so the AP Invoices are closed in the legacy system and so there is not an invoice in SAP B1).
How should these outstanding checks be entered / accounted for so that when the first bank reconciation is completed and the checks clear so that the balance will reconcile to the bank statement?
SAP Business One 2007 A 8.00.230

If you put your cheque number in the journal entry as Reference 1 it will appear in your bank reconciliation, this can be done at line or at header level, depending on how many cheques you post in each journal.
It is usual practice when setting up a new system to create journal entries when setting up the opening balances - stock, debtors & creditors will all offset into an "Opening Balances" suspense account. When you post an entry to create the opening balance sheet, this account should become 0, as the balance sheet will always balance. These open items from your bank reconciliation are simply part of the opening balances.

Distributed check reconciliation (HR//FI)

Similar Messages

Maybe you are looking for