on 11-21-2014 11:06 AM
Hi guys,
I am pushing a set of data through to another application, and I want to then run the currency translation on the other side (it isn't being done in the source system).
So, two questions:
1. Does it matter if the Logic to be run in the destination model is a "standard" script (In this case FXTRANS)?
2. If my ACCOUNT dimension has a different name in the other model, is there an equivalent to the *RENAME function in the *DESTINATION_APP logic?
On one side, it's called ACCOUNT and on the other ACCOUNTC. Similar issue with ENTITY.
This is my script so far:
*SELECT(%ENTS%,LEGALENTITY,COMPANYCODE,ID=%COMPANYCODE_SET%)
*START_BADI RUNLOGIC_PH
QUERY=OFF
WRITE=ON
VALIDATION=OFF
DEBUG=ON
LOGIC=FXTRANS.LGF
APP=Consolidation
//SKIP the dimensions that are not required in destination model - I get errors without this section
DIMENSION ACCOUNT = <NONE>
DIMENSION AUDITID = <NONE>
DIMENSION DEPARTMENT = <NONE>
DIMENSION ENTITY = <NONE>
DIMENSION LIKEUNLIKE = <NONE>
DIMENSION COMPANYCODE = <NONE>
//Set dimension members for called file - as you can see, there are dims with the same TYPE but a different name
DIMENSION TIME = %TIME_SET%
DIMENSION CATEGORY=%CATEGORY_SET%
DIMENSION ACCOUNTC = <ALL>
DIMENSION AUDITIDC = INPUTLOAD
DIMENSION FLOW = <ALL>
DIMENSION GROUPS = G_NONE
DIMENSION INTERCO = NON_INTERCO
DIMENSION LEGALENTITY = %ENTS%
*END_BADI
My UKJT log shows this:
LOG:
FILE:\ROOT\WEBFOLDERS\APPSET\ADMINAPP\Management\TEST.LGF
USER:JMAIDMENT
APPSET:XXXX
APPLICATION:Consolidation
Invalid dimension "AUDITID" in model "Consolidation"
Error in RUNLOGIC call.
BADI EXECUTION TIME IN TOTAL :0.00 ms.
SCRIPT RUNNING TIME IN TOTAL:0.00 s.
Any advice you can give me would be gratefully accepted! We are running BPC 10, SP8.
Thanks very much,
Jason
Hi Jason,
Please provide:
1. Cube name (source) where the logic with RUNLOGIC_PH is defined.
2. Dimension list of source cube and target - Consolidation
"Invalid dimension "AUDITID" in model "Consolidation"" looks strange...
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vadim,
The source model is called Management, and the destination is called Consolidation (just to keep things straighforward!)
Dimension lists for both are in the original script above (except for TIME and CATEGORY, which are shared). I discovered that I got error messages when I didn't specify every dimension in both models.
Everything in the "//skipped" list, plus TIME and CATEGORY are in the source model.
Everything in the second list is in the destination model.
Hope that makes sense - thanks as always!
Jason
Nope - the error I get is even AFTER I specified all the dimensions.
If I don't I get different errors.
If I don't specify the source dimensions:
Dimension(s) COMPANYCODE not found in Application Consolidation of Application Set
Dimension(s) ACCOUNT not found in Application Consolidation of Application Set
Dimension(s) AUDITID not found in Application Consolidation of Application Set
Dimension(s) DEPARTMENT not found in Application Consolidation of Application Set
Dimension(s) ENTITY not found in Application Consolidation of Application Set
Dimension(s) LIKEUNLIKE not found in Application Consolidation of Application Set
And (of course) if I don't specify the destination dimensions:
Dimension ACCOUNTC not specified and doesn't exist in current context.
(This fails one at a time until I have specified all destination dimensions).
The error in my original post is AFTER I specified all of my dimensions.
Hope that helps, thanks,
Jason
Hi Vadim,
Oh ye of little faith!
OK, so the Planning dimensions are as follows:
ACCOUNT (type A)
AUDITID (type D)
CATEGORY (type C)
COMPANYCODE (type U)
DEPARTMENT (type U)
ENTITY (type E)
LIKEUNLIKE (type U)
RPTCURRENCY (type R)
TIME (type T)
Consolidation dimensions are:
ACCOUNTC (type A)
AUDITIDC (type D)
CATEGORY (type C)
FLOW (type S)
GROUPS (type G)
INTERCO (type I)
LEGALENTTITY (type E)
RPTCURRENCY (type R)
TIME (type T)
Hope that helps - please let me know if I'm missing anything you need.
Thanks again for your help,
Jason
Hi Vadim,
OK RPTCURRENCY added: new log...
LGX:
*START_BADI RUNLOGIC_PH
QUERY=OFF
WRITE=ON
VALIDATION=ON
DEBUG=ON
LOGIC=FXTRANS.LGF
APP=Consolidation
DIMENSION ACCOUNT = <NONE>
DIMENSION AUDITID = <NONE>
DIMENSION DEPARTMENT = <NONE>
DIMENSION ENTITY = <NONE>
DIMENSION LIKEUNLIKE = <NONE>
DIMENSION COMPANYCODE = <NONE>
DIMENSION TIME = 2014.002
DIMENSION CATEGORY=BUDGET
DIMENSION ACCOUNTC = <ALL>
DIMENSION AUDITIDC = <ALL>
DIMENSION FLOW = <ALL>
DIMENSION GROUPS = G_NONE
DIMENSION INTERCO = NON_INTERCO
DIMENSION LEGALENTITY = LE997
DIMENSION RPTCURRENCY = <ALL>
*END_BADI
-------------------------------------------------------------------------------------------------------------------------------------
LOG:
FILE:\ROOT\WEBFOLDERS\BPC_SHOPRITE\ADMINAPP\Management\TEST.LGF
USER:JMAIDMENT
APPLICATION:Consolidation
Invalid dimension "AUDITID" in model "Consolidation"
Error in RUNLOGIC call.
BADI EXECUTION TIME IN TOTAL :0.00 ms.
SCRIPT RUNNING TIME IN TOTAL:1.00 s
The FXTrans.LGF script is the standard one, with just a couple of scoping modifications:
*INCLUDE SYSTEM_CONSTANTS.LGF
*SELECT(%SRCLIST%,"ID","AUDITID","IS_CONVERTED='Y'")
*SELECT(%ENTS%,ID,ENTITY,COCODE=%COMPANYCODE_SET%)
*XDIM_MEMBERSET AUDITID = %SRCLIST%
*XDIM_MEMBERSET ENTITY = %ENTS%
//=============================================
// Currency translation logic
//=============================================
*RUN_PROGRAM CURR_CONVERSION
CATEGORY = %CATEGORY_SET%
CURRENCY = ZAR
TID_RA = %TIME_SET%
OTHER = [ENTITY=%ENTS%]
RATEENTITY = GLOBAL
*ENDRUN_PROGRAM
Hope that's everything - let me know if not.
Many thanks,
Jason
Hi Jason,
You don't have to specify every Dimension in the Model - just those that are different.
Also, when you run script for the 1st time don't use VALIDATION = OFF. This is good only after you know that your script is correct and you want to save additional split of a second.
You can find the transport number if you open any Method in Class ZCL_BPC_RUNLOGIC_PH and go to menu items Utilities -> Versions -> Version Management.
Regards,
Gersh
Hi Jason,
What version (Transport number) you have for RUNLOGIC_PH?
A long time back there was an issue with <NONE>, but it was fixed 3-4 years back.
Regards,
Gersh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.