Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« November 2019 | Main | January 2020 »

December 31, 2019

What to watch out while implementing Close Manager

Today financial close process is a critical challenge to accomplish for an organization; hence to fix this FCCS (Financial Consolidation and Close Cloud Service) has been included with module Close Manager by Oracle. Close Manager enables better tracking of all task involved in month end close cycle. The purpose is to automate the close process via defining close tasks, templates and schedules which can be created monthly, quarterly and annually. It helps users to monitor the task status from dashboard and to view which task are running late, who is responsible and notify the users when required by sending the alerts.

Let us look at some points to watch out while implementing Close Manager:

  • If Integration is not working for either Fusion or E-business suite:

You might come across 'Error 404' or a blank page while running integrated task. This might be because of entering wrong URL in Manage Connections tab for example:

Wrong URL entered: https://xyz.us6.oraclecloud.com

Correct URL enteredhttps://xyz.fa.us6.oraclecloud.com

(After logging into Fusion page, the URL that appears in homepage -is the correct URL to be entered in 'Manage Connections')

Also, in 'Manage Connections'- Protocol, Protocol_BI, Protocol_ESS would always be 'https' and Server, Server BI, Server_ESS would contain the correct integration URL:

image1finalv1.jpg

 image2finalv2jpeg.jpg


You might get an error while running integration for E-business suite like "XYZ is not a valid responsibility for the current user. Please contact your System Administrator." Or "An unexpected error occurred. Please contact your System Administrator" Or "The AP Accounting periods function is not available under the Payables Inquiry-XYZ responsibility "Or "Unable to execute function. (RESP_ID=xxxxx/REP_APPL_ID=xxx)". Following steps could solve the above errors:

Step 1-Create new integration

o   Under properties-select execution type as End user

o   End user Endpoint-Function id and Resp_Appl_id should be same as given in E-business suite. End user Endpoint: $PROTOCOL$://$SERVER$:$PORT$/$CONTEXT$/RF.jsp?function_id=xxxxx&resp_id=$respid$&resp_appl_id=xxx&security_group_id=0

o   In the parameter tab-Select Parameter type as 'Text' and Parameter Code as 'respid'

Step 2-Create a new task type

o   Create a new task type with the integration created in step 1

o   In the parameter tab-Correct Parameter id (responsibility id) needs to be written which should be the same as given in E-business suite

Step 3-Create the EBS integrated task with the new task type under E-business suite (which was created in step 2) 

  • If getting pending status against a task in Schedule Task:

If you are getting 'Pending' status in Schedule Task for a task, that means the schedule created for the task is not open. Status of the schedule needs to be set as "Open".

 Another reason can be that Responsibility in the task has not been selected. To change the Pending Status in Close Manager, task parameters needs to be set when any tasks are added to a template.

image3final jpeg.jpg

  • If getting greyed out responsibility in Parameter tab:

In the above screenshot if this responsibility is greyed out and you are not able to select the responsibility then make sure the same is set for the respective 'Task type' selected in the particular task. 

image4finalv3.jpg
  • Do remember to create a new schedule whenever you edit the task, change the connection, edit the integration tab or edit the parameter in task type.

December 20, 2019

Reconciling Items Conversion Utility

Problem Statement:

Every month after running transaction matching, users were left with few unmatched transactions which were qualifying as reconciling items. For e.g. in control disbursement account, outstanding cheques for a month are reconciling items for that month and should match the GL balance.

Oracle ARCS does not provide the out of box capability to convert these unmatched transactions into reconciling items automatically.

Solution:

Our solution aims at facilitating the movement of unmatched transaction to reconciliation compliance module in ARCS, eliminating user intervention in the process, thereby resulting in complete investment in automation.

This macro based excel utility is developed to convert unmatched transactions in transaction matching to reconciling items in reconciliation compliance in ARCS acceptable file format.

The Source file for the utility will be the extract of unmatched transactions from the corresponding Matching.

Overview of Solution:

The execution of the utility is a 5-step process which includes:

1.      Export unmatched transactions from Matching to prepare the Source File.

1.JPG

2.      Click "Convert to Reconciling Items" command button given against the Account Type in the utility.

2.JPG

3.      Select File to select the source file, saved in Step 1.

3.JPG

4.      Select the Output folder & Output file name for the target file.

4.JPG

5.       Import the target file generated in Step 4 into Reconciliation Compliance as adjustments on the corresponding Account Id.

5.JPG

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter