topic Re: Syntax error when running GLPLUP - Flex Plan Upload in Application Development and Automation Discussions

Syntax error when running GLPLUP - Flex Plan Upload

roy_orosz4 — Wed, 17 Dec 2008 22:30:11 GMT

HI,

We want use transaction GLPLUP to perform a Flex Plan Upload, but encounter a syntax error in program RK50003 stating:

The following syntax error occurred in program "RK500003 " in include

"PP_FISL_GINC " in

line 652:

"The data object "ITDAT1" does not have a component called "XBILK"."

" "

This program is a local object, and appears to be generated by SAP. Checking the program attributes the owner and the last person to change this program is a consultant who has rolled off the project, and is not available for help.

I suspect that there must be some steps to regenerate this code, but I am not certain where to look for this information.

I have tried running GLPLDEL and GLPLINSTALL, but this did not change RK500003.

Any insight you can provide on this is greatky appreciated.

Thanks,

Roy

Re: Syntax error when running GLPLUP - Flex Plan Upload

Former Member — Wed, 04 Feb 2009 07:26:46 GMT

Hi Roy,

After applying some new support packages, I got the same error as you describe. So, I wonder how you did to solve this? Any help is much appreciated.

Re: Syntax error when running GLPLUP - Flex Plan Upload

roy_orosz4 — Wed, 04 Feb 2009 13:31:13 GMT

HI,

I reported this issue with SAP and the following is what they had me do to resolve the issue:

1. Run transaction GLPLDEL:

Deletes all generated reports of the planning processor for

FI-GL/SL planning (application class GLU1). After a new call of

the planning, these reports will be generated once again.

2. Run transaction GLPLINSTALL:

It regenerates necessary database table entries for FI-G/SL Planning

(tables t8pl*). Make sure that you will perform this step when no

posting of FI-SL data is running.

This resolved the issue for us.

Good luck,

Roy

Re: Syntax error when running GLPLUP - Flex Plan Upload

Former Member — Thu, 05 Feb 2009 06:58:00 GMT

Thanks for your reply. I will try this.