Forum Stats

  • 3,827,873 Users
  • 2,260,836 Discussions
  • 7,897,401 Comments

Discussions

FDMEE No Records Warning on Import on TDATASEG

User804054-Oracle
User804054-Oracle Member Posts: 7
edited May 16, 2017 11:19AM in Financial Data Management

Dear All,

we are trying to load data from a relational table into FDMEE through an Open Interface Adapter.

We succeed in loading data on Open Interface Table, as we can see them through SQL Developer (import fish gets grey).

However, we receive a warning from the FDMEE process Log. Into the log we find the following:

2017-05-15 16:47:15,699 WARN  [AIF]: Warning: No records exist for Period 'Sep - 2015'

....

2017-05-15 16:47:16,183 DEBUG [AIF]: CommMap.validateData - START

2017-05-15 16:47:16,183 WARN  [AIF]: Warning: The Import step has not been completed for period Sep - 2015

2017-05-15 16:47:16,183 DEBUG [AIF]: CommMap.validateData - END

We believe there is something weird on period mappings we didn't cope with.

We tried to perform the integration with Period Global Mapping first and then with Application Mapping, with no successful results.

Could you please support?

Answers

  • JohnGoodwin
    JohnGoodwin Member Posts: 30,471 Blue Diamond
    edited May 15, 2017 1:19PM

    Have you tried setting up period mappings in the source mapping tab, select the source system as the open interface table and define the mappings, in the load rule you should be able to select the calendar.

    Cheers

    John

  • Francisco Amores
    Francisco Amores Member Posts: 1,694 Bronze Crown
    edited May 15, 2017 2:48PM

    Vito :-)

    1) check that data exists in AIF_OPEN_INTERFACE

    2) check that you are passing the correct Batch name in the DLR parameter

    3) try first with no period mapping

    Once that's working, it means data was pulled from AIF_OPEN_INTERFACE to TDATASEG_T

    4) Then setup the source period mappings as John suggested

    REgards

  • User804054-Oracle
    User804054-Oracle Member Posts: 7
    edited May 16, 2017 4:00AM

    Hi John

    in the beginnnig i had set the period mappings in the source mapping tab but the

    results was the same. let me try again.

  • SH_INT
    SH_INT Member Posts: 3,192 Bronze Crown
    edited May 16, 2017 4:30AM

    Got to the session execution in the ODI Operator and look at the Print Variables step. That will tell you the value for the p_period_key variable which is what the process will use to determine what period to import the data for. If there is an issue with the Period mapping you will see it here

  • User804054-Oracle
    User804054-Oracle Member Posts: 7
    edited May 16, 2017 4:32AM

    Hi Curro,

    1) -> yes, tha data are loaded into AIF_OPEN_INTERFACE

    2) what does exactly means  "the correct batch_name".  Does the batch name has to respect some standard?

    In the DLR panel (for this FDMEE release 11123.700) there isn't  (I didn' t find) the way  to set the batch name into Source Option tab of DLR.

    In this FDMEE (11123.700) does exist another way to set the Batch Name that I have already written into AIF_OPEN_INTERFACE_TABLE?

  • SH_INT
    SH_INT Member Posts: 3,192 Bronze Crown
    edited May 16, 2017 4:43AM

    The Open Interface Adapter comes with 2 source filter parmeters by default

    1) Batch Name

    2) Delete Data After Import

    These can be seet on the DLR screen in the Source Filter section at the bottom

  • User804054-Oracle
    User804054-Oracle Member Posts: 7
    edited May 16, 2017 11:19AM

    John, Francisco, SH_INT

    the import warning has been solved.

    There was some setting wrong in Period Mapping section.

    In particular some Application mapping periods were set in a wrong way in respect to the "global mapping setting".

    The script Befimport has been modified to insert the correct period, as defined into "Global mapping".

    thanks everybody

    Regards

This discussion has been closed.