cancel
Showing results for 
Search instead for 
Did you mean: 

indicator not determined for period 1 for VA01 in China Client

Former Member
0 Kudos

Dear Guru

I am handling Chinese Client

During Standard Sales Process in Chinese Login I am Getting Error "Indicator did not determine the period 1"

as I am Using Standard Sales Area 1000-10-10 and Order type TA (as Per German SAP Standard)

The Description for the Above error is pasted here

Indicator did not determine the period 1

Message No. VD346

Diagnosis

Enter the identification period is not defined.

Step

You can use F4 to display the logo of the period allowed values​​.

And even I searched the Forum for Message No. VD346 I got TPRG table to be updated, but the solution was not satisfactory so kindly give me some more inputs regarding this and help me in solving the issue.

Regards

Kiran Nazare

Accepted Solutions (1)

Accepted Solutions (1)

Shiva_Ram
Active Contributor
0 Kudos

During Standard Sales Process in Chinese Login

Did you see entries in Chinese language in table TPRG? If not maintain similar to EN or DE language in it using t.code SM30 and then check again.

Regards,

Answers (4)

Answers (4)

Former Member
0 Kudos

Thanks For the Guru

For taking Keen interest in Solving the issue.

The Steps taken to solve the issue

1. Identified the Data Present in TPRG table

2. With the help of ABAPer the Table data in english(EN) was copied to Chinese Language (ZH)

By these extension the Problem got solved and hence I am Closing the Threat

Once again thanks for the Support extended

Regards

Kiran Nazare

Lakshmipathi
Active Contributor
0 Kudos

Check the following note:-

Note 28717 - VD346: Period indicator 4 is not defined

G. Lakshmipathi

jpfriends079
Active Contributor
0 Kudos

This is related Date conversion.

Following are some the program for the error:

- LBORRTU05

- LVDATU01

- LVDATU02

If Revenue Recognition is active then you can refer following SAP Note 1306199 - Incorrect subitems for category A period shift.

If problem persist then either take help of ABAPer and debug or write to SAP for this.

Regards

JP

Please note: Frankly I never came across this kind of error.

What I have suggested, is purely on the bases of my work around on this error.

Former Member
0 Kudos

Hi,

Refer OSS Note :- 456261

Ram