PO Field Selection Key "NBF" Changes - Impact?

[Former Member]

Hi all,

We have SAP Standard Field Selection Key "NBF" is being assigned to NB and other PO document types in customizing.

There are already PO's existing in Production System with PO Document Type "NB" with Combination of "NBF".

To handle some new requirement, we thought of Creating a new Field Selection Key (Example: "ZBF") and assign to existing PO document type "NB".

We would like to know the impact on existing PO's when we change the Field Selection Key.

Please share your experience if any.

Thanks

Ram

[former_member187965 · Accepted solution]

Hi,

It will not have any impact on old PO unless and until you make changes in old PO after assigning the new field selection key.

[Former Member · Accepted solution]

Okay. Thanks.

[former_member210560]

Dear Ram,

In F1 help of the field tax code, it clearly informed do not change the tax code and the old value

must remain when you have an open items.

Regards,

ian Wong Loke Foong

[Former Member]

Hi all,

I'm looking for other possible answers from anyone from their experience, in terms of Impact if any.

I would like to wait for some more time/days. Till such time, this thread will be open.

Thanks

Ram

[JL23]

Can you give an example what exactly you want to do?

I do a lot system migrations SAP to SAP. I often see the dead bodies in the cellar.

Example: A field is made hidden, and after some time nobody remembers that field and that many old data had even a value in this field.

So this field is not mapped, but a value is carried over if data is migrated using ALE technique to send the data by IDOCs.

This usually ends in a error as the content of this field is not customized in the target system.

so I just can recommend, if you change settings from optional to mandatory, then make sure that you fill this field in all existing data to be consistent.

if you hide a field, then remove the content in any old data.

e.g. for POs you can use MEMASSPO for a mass maintenance.

This recommendation is even valid if you do not consider to harmonize systems some day in future, because I often saw incidents about "ghost values",  People got values in a report or even on a PO form and could not imagine from where this value was taken. Hiding field does not make the value going away.

[Former Member]

Hi Jurgen L,

Currently we have multiple PO Document Types. Field Selection Key NBF is being assigned to most of the PO Document Types.

We have a requirement to have Tax Code field as Mandatory to Purchase Orders which are related to PO Document Type as NB. Current Tax Code setting is Optional for field Selection Key NBF.

We already have multiple PO's created with NB and NBF combination in our Production system.

Since, NBF Field Selection Key is assigned to NB and other PO Document Types, we are thinking to copy NBF and create a new Field Selection Key as ZBF.

Then, for new Field Selection Key ZBF, we are planning to make the Tax Code field as Mandatory.

Then, assign this Field Selection Key ZBF to existing PO Document Type NB.

We would like to know, Is there any Impact on existing Purchase Orders in ECP which has the combination of NB Document Type PO's with NBF Field Selection Key.

Thanks

Ram

[JL23]

in this matter I share the optionion of shailesh kurdukar

if you change an older PO, then you will receive a error to complete the data.

[Former Member]

Hi Jurgen and Shailesh,

I understood, after Tax Code Mandatory and After assigning new Field Selection Key "ZBF" to Existing PO Document Type "NB", if we try to change any old PO, then it will ask us enter the tax code, (Since it is mandatory).

Since "Tax Code" mandatory is the actual requirement, can we do a mass update to all existing PO's with "Tax Code" as "I0 - No Tax"?

For your information, Some materials are taxable and some materials are non-taxable (tax exempt). and the existing PO's are in the following status. Just Created, Partially Received and Partially Invoiced and Fully Invoiced. So how can we go head on this?

If we update some Tax Code by mass update, how this will impact during Invoice Posting?

Please advise.

Thanks

Ram

[former_member210560]

Dear Ram,

In your scenario, i think better you create a new document type like ZNB assign to FSK "ZBF".

In the mass maintenance, the system does not change the following fields MWSKZ and also

you have partial items in process.

Regards,

ian Wong Loke Foong

[former_member210560]

Dear Ram,

All document NB will follow the behaviour for ZBF settings.

Regards,

ian Wong Loke Foong

[Former Member]

Okay. Thanks.