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.
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
in the beginnnig i had set the period mappings in the source mapping tab but the
results was the same. let me try again.
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
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?
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
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".