Load Flat File into BW-BPS

[Former Member]

Dear all,

At the moment we're facing a problem related to the load of a FLAT File

into BW-BPS.

We implemented the setup as described in "How to load a Flat File into BW-BPS".

Specifically, every time when a file is loaded via the Planning Function, the following message appears: "UPC204 - Value 20 for

characteristic Value type is not contained in the relevant selection

conditions"- .

In the Planning Level and Package, the characteristic for Value Type is

set to 20. In the function builder (Z_SEM_BPS_EXIT_FILE_LOAD_INIT) the

value for 0Vtype is hardcoded as '020', the number of characteristics

is to 3.

In the function builder we added the leading zero, removed it, add

a space. Still the problem persists.

For another info object 0version (hardcoded as 001), we don't face any problems.

In which direction should we investigate?

Thanks for your suggetions.

Kurt

[Former Member · Accepted solution]

Kurt,

Few things to check

1)Check your Planning level to see you have 20 selected against Value Type for Reporting Characteristic

2)In your text file have the header row with "0VTYPE(3)"

3) The value in the text file should say "020"

If you have all this set correctly then go and check master data table for 0VType to see it has 020. If you have all this set correctly it should work.

Hope this helps

Thanks

Bhavesh

[Former Member · Accepted solution]

Dear all,

Thanks for your replies.

We discovered that our programmer made a mistake in the function module.

Best regards,

Kurt

[hendrik_brandes]

Hi Kurt,

is the field "Value Type" within the list of changable fields which will be maintained in the definition of your planning function?

Regards,

Hendrik

[Former Member]

Hi Hendrik,

The Field "Value Type" isn't included in the List to be changed.

Actually it isn't either in the Field List.

Kurt

[Former Member]

Hi Kurt,

If it is not there in the field list then the fields are missing in your Planning Level/Package.

Once you have selected it there you would be able to see it in the field list and include it in the Fields to be changed in the Planning Function.

Bye

Anurag

[Former Member]

Anurag,

Strange but 0VTYPE is definately defined in my level

and package.

Maybe because 0VTYPE isn't in my header characteristics?

Kurt

[former_member93896]

Hi,

To clear up the confusion, if a field is hardcoded to a single value in the level, then the field can not be changed. There for the field will not appear in any field list.

Regards

Marc

SAP NetWeaver RIG