Incoterms Field editable mode for Return Sales Order.

[Former Member]

Hi,

I am facing one issue that the "Incoterms field" in the "Return Sales Order" that reference to a billing document, the system executing default non-editable mode.

But my client requirement should be editable mode.

Kindly help me to resolve the issue.

Regards,

Saravenakumar.K

[former_member200027 · Accepted solution]

Hello Saravenakumar.K,

I would suggest checking whether you have any customer codings in
FORM USEREXIT_FIELD_MODIFICATION in program MV45AFZZ,

since this is the userexit used to control whether a field is changable or not.

You may also check note '208245 - Availability of fields in sales orders' for
detailed information.

Best regards,
Crystal Lin

[Former Member · Accepted solution]

Hi Crystal Lin,

You are correct. Actual earlier they blocked the Incoterms field for edit due to audit purpose.

Thank you for your valuable input.

This conversation can be closed.

Regards,

Saravenakumar.K

[former_member216345]

Hi,

Is this issue coming only when you are creating the order w.r.t. billing document or also when you are creating a standalone returns order without reference to invoice? Is it coming only for returns order?

Regards,

Onkar

[jobis]

Hi Saravana,

If you are using std copying control routines, then the inco term field will be coming as modifiable.

Please check the copying control VTAF, header level, 'data t' fields, You may be using custom routines for the business data.

Else, there may be an enhancement/exit coded for making it non modifiable.

Check that

Regards

Jobi

[Former Member]

Hi Onkar,

I unable to modify this Incoterms in both normal sales orders and return sales order also. 

Regards,

Saravenakumar.K

[Former Member]

Hi Jobi,

Copy control is using for copy the data from source to target.

But my requirement is, need editable mode for Incoterms field in Sales order.

[former_member216345]

This can be due to 2 possible reasons:

1. Field specific authorization to the user

2. A screen variant may have been assigned in the VA01 transaction in order to restrict this field.

It will be only for one of these  reasons that the field is not editable.

[jobis]

HI Saraven,

If so, did u check user exits or enhancemnt in the program, as suggested?

Jobi