Load infoprovider in 2 steps (2 transformation files) - BPC 10.0

Question

Hi Masters,
For your better understanding, the background of this issue is that I currently have the planning solution configured and in use in BPC 7.50, in another
server, and on it I have the same ACTUAL uploading process from our legacy system (SIG) working just perfectly.
PS: The process chain to load transaction data from BW infoprovider using 2 transformation files was configured by SAP consulting, since this was a project made by SAP consulting.
So, I am migrating the solution to BPC 10.0, and is better to say "reconfiguring" the solution to BPC 10.0. I just recriated the transformations and convertion files, the process chain (and all its custom variants) and the data package. But in the new configuration, I am unfortunately facing this problem whlie executing the Process Chain.
Data Package Script:
INFO(%InforProvide%,GIF00003)
INFO(%TRANSF1%,\ROOT\WEBFOLDERS\GIF_TEMPLATE\CR_INCOMESTATEMENT\DATAMANAGER\TRANSFORMATIONFILES\CR_IST_LOAD_SIG_STEP1.xls)
INFO(%TRANSF2%,\ROOT\WEBFOLDERS\GIF_TEMPLATE\CR_INCOMESTATEMENT\DATAMANAGER\TRANSFORMATIONFILES\CR_IST_LOAD_SIG_STEP2.xls)
'Handling of records in target (0 = Append, 1 = Overwrite, 2 = Replace )
INFO(%TARGETMODE%,0)
INFO(%RUNLOGIC%,1)
INFO(%CHECKLCK%,1)
INFO(%KEYDATE%,0)
INFO(%TEMPNO1%,%INCREASENO%)
INFO(%ACTNO%,%INCREASENO%)
'Upload data from SIG - 1st Step
TASK(ZGIF_INFOPROVIDER_CONVERT1,OUTPUTNO,%TEMPNO1%)
TASK(ZGIF_INFOPROVIDER_CONVERT1,ACT_FILE_NO,%ACTNO%)
TASK(ZGIF_INFOPROVIDER_CONVERT1,TRANSFORMATIONFILEPATH,%TRANSF1%)
TASK(ZGIF_INFOPROVIDER_CONVERT1,SUSER,%USER%)
TASK(ZGIF_INFOPROVIDER_CONVERT1,SAPPSET,%APPSET%)
TASK(ZGIF_INFOPROVIDER_CONVERT1,SAPP,%APP%)
TASK(ZGIF_INFOPROVIDER_CONVERT1,FILE,%InforProvide%)
TASK(ZGIF_INFOPROVIDER_CONVERT1,KEYDATE,%KEYDATE%)
TASK(ZGIF_CRLOAD_LOAD1,PREPROCESSMODE,0)
TASK(ZGIF_CRLOAD_LOAD1,TARGETMODE,%TARGETMODE%)
TASK(ZGIF_CRLOAD_LOAD1,INPUTNO,%TEMPNO1%)
TASK(ZGIF_CRLOAD_LOAD1,ACT_FILE_NO,%ACTNO%)
TASK(ZGIF_CRLOAD_LOAD1,RUNLOGIC,%RUNLOGIC%)
TASK(ZGIF_CRLOAD_LOAD1,CHECKLCK,%CHECKLCK%)
TASK(ZGIF_CRLOAD_LOAD1,KEYDATE,%KEYDATE%)
'Corp Unit Calculation (upload base level companies with negative signal) - 2nd Step
TASK(ZGIF_INFOPROVIDER_CONVERT2,OUTPUTNO,%TEMPNO1%)
TASK(ZGIF_INFOPROVIDER_CONVERT2,ACT_FILE_NO,%ACTNO%)
TASK(ZGIF_INFOPROVIDER_CONVERT2,TRANSFORMATIONFILEPATH,%TRANSF2%)
TASK(ZGIF_INFOPROVIDER_CONVERT2,SUSER,%USER%)
TASK(ZGIF_INFOPROVIDER_CONVERT2,SAPPSET,%APPSET%)
TASK(ZGIF_INFOPROVIDER_CONVERT2,SAPP,%APP%)
TASK(ZGIF_INFOPROVIDER_CONVERT2,FILE,%InforProvide%)
TASK(ZGIF_INFOPROVIDER_CONVERT2,KEYDATE,%KEYDATE%)
TASK(ZGIF_CRLOAD_LOAD2,PREPROCESSMODE,0)
TASK(ZGIF_CRLOAD_LOAD2,TARGETMODE,%TARGETMODE%)
TASK(ZGIF_CRLOAD_LOAD2,INPUTNO,%TEMPNO1%)
TASK(ZGIF_CRLOAD_LOAD2,ACT_FILE_NO,%ACTNO%)
TASK(ZGIF_CRLOAD_LOAD2,RUNLOGIC,%RUNLOGIC%)
TASK(ZGIF_CRLOAD_LOAD2,CHECKLCK,%CHECKLCK%)
TASK(ZGIF_CRLOAD_LOAD2,KEYDATE,%KEYDATE%)
Process Chain
    2. Error
    3. Variant Configuration (ZGIF_INFOPROVIDER_CONVERT2)
    4 . Error Package
So, what I need is to understand if there was any change between BPC 7.50 and BPC 10.0 (regarding this custom variants), that is preventing the new configuration to work as it should, or better saying, as I already have working in BPC 7.50.
I checked already the variants configurations and the Data Package Script, to certify that everything is correct, and it seems perfect!
The strange thing is that the process chain executes the first Convert (ZGIF_INFOPROVIDER_CONVERT1) with no problem, and it is exactly the same configuration as the second Convert.
    5. Variant Configuration (ZGIF_INFOPROVIDER_CONVERT1)
Should I use other variant between the first Load and the second Convert?
I hope you guys can help me to solve this question.
PS: The transformation files are attached to this message.
Thanks in advance!
Adriano Frossard
São Paulo - Brazil

Answer 1

Hello Adriano,
I have small question here,
are you automate the entire process...?
if manually running the data manager package, is it successful or abort...?
As far as I know variant comes into picture while automating the process only...
recently we also face the same issue, while automating the process at that time we use RFC system name, unfortunately the user doesn't have required access to perform the task. while doing it manually its successful but throwing an error while running from back end...
In this case the problem with variant so the transformation file doesn't throw any error , its show the validation is successful..
Please check the variant is available or not...
if possible can you please share the log abort  DM package...
Regards,
SRG...