Impact of extending KNVP-PARZA length

[trisno_s]

Hello,

I'm an SD consultant, working in a company that has business need to assign more than 999 Ship-to-Party to 1 Sold-to-Party. I've searched the forum and to make system accommodates the change, is to extend KNVP-PARZA length from 3 to certain number needed (what the company needs is 5, for up to 99999 Ship-to-Party).

However, we know that KNVP-PARZA is standard field of SAP. Is there any impact of forcibly extending its length? Has anyone ever tried to extend it? Is there any additional steps we need to do after extending its length - since the system has been running for years with its default length.

Please share your experience.

Thank you,

Trisno.

[trisno_s · Accepted solution]

After long discussion, the management has decided to use few Customer numbers with their names and addresses being maintained separately per transaction using Texts. We have to modify several reports to make sure these Texts show up properly.

[jignesh_mehta3]

Hello,

Have a look at SAP OSS Note 1452390 - Error Message: F2 699 - 'There are already 1000 entries for function SH' in transaction XD02, which applies to all Product versions including the following:

SAP ERP all versions

SAP R/3 Enterprise all versions

SAP R/3 all versions

The Note also provides recommendations by means of workarounds.

Bottomline, it is not possible to extended KNVP-PARZA more than 999. Still your client insists on this change, please raise a OSS Message to SAP.

Thanks,

[Lakshmipathi]

Not possible as per OSS note 2904323

[trisno_s]

Hi Mr. Laksmipathi,

Thanks for your response. I forgot to mention that the company is still using SAP 4.6c version.

The OSS note you mentioned only includes SAP HANA version, yes?

So, is it possible to extend KNVP-PARZA length in SAP 4.6c version without any repercussion?