BPS Post Processing Question

Question

Dear All,
We have an EXIT function which resides in one planning level and the planning layout in another planning level.
The EXIT function is calculating the numbers correctly which creates internal table XTH_DATA and passes it to function module UPF_PARAM_EXECUTE. When we check XTH_DATA, the data records are as we need the records to be generated.
The issue we are having is that, when the EXIT funciton has completed, the data in XTH_DATA looks perfect. However, the data saved to infocube is not exactly the same as it created. For example, the EXIT creates data for 2007/001 - 012. The resulting data in infocube contains many entries of fiscal period 2006001 through 2006006. The posting period is left blank from EXIT function. The resulting data has posting period of blank, 1 through 6, etc.
We use request ID to diaplay data and makes sure the data source is correct.
Planning level for EXIT function data model:
Characteristics are:
Assortment Type
Base Unit
Climate Zone
Concept
Department
Distribution Channel
Fiscal year
Fiscal year/period
Fiscal Year Variant
Hierarchy ID
Lifestyle
Local currency
Plng Area
Posting period
Sales Organization
Version
Volume Group
Key Figures are:
Balanced Receipts
Number of Stores
Stock Index
Any helps, comments, and/or hints are greatly appreciated.
Best regards,
Sam

Answer 1

Highly frustrating. I've got the IPlanetDirectoryPro SSO token being set, but the custom code to add additional domain cookies...those are not re-written by the cdservlet, and even if hard-coded for testing (I assume I can parse the domain/URI being requested by parsing the HttpServletRequest, but am just testing now) to the 'new domain,' they are sent but discarded by the browser.
This is bad, as those custom cookies are required by several apps. Is there any documentation on writing a custom cdcservlet, sample code, code for the existing one, or any other means to do this?
To be clear - 'basic' CDSSO seems to be working, if a request is made to a resource on Domain B, it directs to the AM host, which is in Domain A. The IPlanetDirectoryPro cookie is being set for Domains A and B in this case, and accepted by the browser. That setting I finally found in AMAgent.properties, here:
com.sun.am.policy.agents.config.cookie.domain.list (in case this helps someone else in the future)
However, I have post-process code implementing AMPostAuthProcessInterface which was setting custom cookies required by some apps, and I am unable to change the domain these are set in. More accurately, I can change the domain, and the data is sent, but the browser is then rejecting it, presumably as it's seeing it as a cross-domain cookie, and thus bad/discarding.
This seems to only leave me with trying to use a custom cdcservlet, assuming I can find the existing code or similar to start with, as I have no idea how it's avoiding the cross domain cookie issue..
Anyone?