Redwood BPA Select Option Parameter not Populating in Temporary Variant

[Dallas1]

Hi,

I am trying to submit a program from BPA using a temporary variant, and calculating a date parameter (S_DATE) as from the previous month 11th day to current month 10th day.

In the job definition, I define SEL_S_DATE as a In/String, calculated at runtime, with the expression:

=Time.format(Time.expression(Time.now(),'subtract 1 month set day 11'),'yyyyMMdd') + ' - ' + Time.format(Time.expression(Time.now(),'set day 10'),'yyyyMMdd')

I have TEMPORARY_VARIANT set to "Y". The Definition was copied from SAP_AbapRunPrintExt. I want it to use the default selection screen, with the exception of populating the S_DATE field as described above.

When I submit the definition, the parameter doesn't populate, it instead is left as the default value when running the report.

When I view the parameters, I can see that SEL_S_DATE was correctly calculated as "20190411 - 20190510" (Without the quotes), but this doesn't make it to the temporary variant.

I'm not getting any errors in BPA or ERP, and no short dumps, no authorization failures.

I've tried using System_DynamicTrace with jobservice, connector, and jobfile = debug, but can't find any errors related to this parameter transfer to SAP.

Does anyone have any further ideas?

Thanks!

[gmblom · Accepted solution]

Thanks Dallas,

Sorry for pondering over this for a couple of days. Indeed, the transports are not required anymore if you have an SAP system that is up to date.

You can disable the usage of the Redwood transports by adding Process Server parameter SAP_UseTransports with value 'false' on the SAP Process Server. Then restart the Process Server to make the parameter active.

Regards Gerben

[Dallas1 · Accepted solution]

That seems to have solved it! Thanks Gerben!

I couldn't find much documentation about this parameter... is there any negative impact to setting this parameter to "false" on all of our SAP Process Servers?

Thanks again,

Dallas

[Dallas1]

Hi Gerben,

In the stdout.log from the Dynamic Trace, I can see the following:

...command.JobParameterHelper - getJobParameterUppercase: TEMPORARY_VARIANT=Y

...

...command.AbstractXbpJobRunCommand - Adding select option (4) S_DATE = 20190411 - 20190510

execute /SCJS/XBP_JOB_ADD_ABAP_STEP

This is the only reference in the file to the S_DATE, and after that, there are no errors in the log, and ends successfully:

sap status F deleted=false killed=false canceled=false final job status Completed

I can't find any useful information in the "Get Support Files" option of the dynamic trace, searching for the program name, job name, parameter name, or temporary_variant.

Thanks,

Dallas

[gmblom]

That information looks good, now we need to figure out why it does not work.

In the trace you should find the transaction that is send to the BAPI to setup the temporary variant. Can you check if this one contains the correct information?

Regards Gerben

[Dallas1]

Hi Gerben, sorry I replied to the main thread again...

Here's what I've tried since yesterday...

I placed external breakpoints in the following four RFC FMs in ERP, and run the job...

/SCJS/XBP_JOB_ADD_ABAP_STEP
BAPI_XBP_JOB_ADD_ABAP_STEP
/SCJS/XBP_VARIANT_CREATE_L
/SCJS/XBP_VARIANT_CREATE

The process breaks in at /SCJS/XBP_JOB_ADD_ABAP_STEP, but never calls the other FMs. I notice that /SCJS/XBP_JOB_ADD_ABAP_STEP does not have the export parameter for "TEMP_VARIANT" or the SELINFO table, which BAPI_XBP_JOB_ADD_ABAP_STEP does have...

Should I be expecting a call to BAPI_XBP_JOB_ADD_ABAP_STEP? Or should /SCJS/XBP_JOB_ADD_ABAP_STEP have those parameters?

I asked our Basis team to import the transports available in BPA through the Configuration -> Software section (Filename is SAP-BPA-Redwood-XBP-46c-710-9_1_0_6.zip), but after import, the interface of /SCJS/XBP_JOB_ADD_ABAP_STEP still doesn't contain those parameters. (On that note, the transport available in this file is I46K000754, which shows it was exported from I46 on 07/03/2013)

I've also tried using both the SAP_AbapRunPrint AND the SAP_AbapRunPrintExt, and neither of these are working to create a temporary variant.

I'm not sure what else I can try at this point...

Do you have any further ideas? Should this be calling BAPI_XBP_JOB_ADD_ABAP_STEP? And if so, how do I configure BPA to use that FM?

Thanks!

Dallas

[Dallas1]

Hi Gerben, thanks for your response!

I tried adding [ ], this didn't seem to help. I can see SEL_S_DATE in the job parameters after running shows up as [20190411 - 20190510], but it still populated the default date on the variant (05/01/2019 - blank).

In the trace log I can see:

AbstractXbpJobRunCommand - Adding select option (4) S_DATE = 20190411 - 20190510

I can't find any errors related to this in the System_DynamicTrace log or support files. (Ran with your suggestion of connector.sap.rfc=debug)

SAP_Info shows XBP 3.0 is enabled, and only the following entries contain the word "Variant":

Line 57: XBPLongVariantValuesAvailable : true
Line 58: RedwoodLongVariantValuesAvailable : true
Line 81: XBPLongTemporaryVariantValuesAvailable: true
Line 90: EnableVariantsList : false

Thanks,

Dallas

[gmblom]

Hello,

Can you try adding [] around the expression?

='[' + Time.format(Time.expression(Time.now(),'subtract 1 month set day 11'),'yyyyMMdd') + ' - ' + Time.format(Time.expression(Time.now(),'set day 10'),'yyyyMMdd') + ']'

You can add trace string connector.sap.rfc=debug to see what is going on.

Also run SAP_Info, check if support for temporary variants is available on the connector.

Regards Gerben

[Dallas1]

Sorry, I accidentally responded at the top level. Thought I'd add that here in case you have notifications turned on.

Dallas