The RM job runs in generate and execute mode. I uploaded the generated ABAP and tried to run in preloaded mode. Several R3 DFs run successfully. Then the job hits an R3 DF that passes a global var ($G_SDATE) and fails. The var is a date and is being compared to a date in SAP. The var is being set with to_date() in the job execution properties and a print statement verifies it is being set. There is a second param that is being set the same way.
The error message is:
2096 5196 R3C-150412 3/10/2009 7:28:53 PM |Dataflow DF_VendorItemsFact_SAP
2096 5196 R3C-150412 3/10/2009 7:28:53 PM R/3 CallReceive error <Function Z_AW_ABAP_RUN: . Enter date in the format //>.
4364 5952 R3C-150412 3/10/2009 7:28:53 PM |Dataflow DF_VendorItemsFact_SAP
4364 5952 R3C-150412 3/10/2009 7:28:53 PM R/3 CallReceive error <Function Z_AW_ABAP_RUN: . Enter date in the format //>.
The attached zip file contains the atl for the DF and the generated ABAP for one of two R3 DF’s.
I came accross this error in the SAP Rapidmarts, and in my case it was a bit misleading so I wanted to document it in case anyone hits this.
The date format in the error message is slightly different for my error;
RFC CallReceive error <Function Z_AW_ABAP_RUN: . Enter date in the format ..____>.
Strangely, the flow worked fine in generate and execute mode, rather than preloaded.
I couldn’t find anything wrong with date parameters, so I had a look at the actual contents of the preloaded program.
It turns out that in the ‘out-the-box’ rapidmart code there are multiple R3 dataflows that use the same ABAP program name. This is fine in generate and execute mode, but not if the programs are preloaded.
I used the automated SDS-to-SAP program upload, so it generated the program once then overwrote the program for the next R3 flow with the same program name.
One of the flows had multiple date parameters passed in, the other didn’t - the result was this error message.
Changing the program name and re-loading the ABAP fixed this.
Just watch out for duplicate program names in the rapidmarts.
Thanks Douglas, that’s one of the things I would have never dreamed about looking at. I am sure it will help others as well. And I will notify the RapidMart team to run a check.
Thank you for this info, it saved me from many sleepless nights My question is, 11 rapidmart packages come with a total of more than 500 r3 dataflows meaning 500+ programs in the sap system. Is there any way to mass-change abap program names for these data flows? I’d like to use such a naming convention as ZBO_R3DATAFLOWNAME.
(BOB member since 2006-03-27)
(BOB member since 2004-12-17)
(BOB member since 2006-03-27)
My question is, 11 rapidmart packages come with a total of more than 500 r3 dataflows meaning 500+ programs in the sap system. Is there any way to mass-change abap program names for these data flows? I’d like to use such a naming convention as ZBO_R3DATAFLOWNAME.